From: Scott Wood <scottwood@freescale•com>
To: shiva7 <sivasakthi7@outlook•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: questions on CONFIG_PPC_ADV_DEBUG_REGS, DBCR0_BRT, and DBCR0_ACTIVE_EVENTS
Date: Thu, 29 May 2014 16:08:28 -0500 [thread overview]
Message-ID: <1401397708.6603.182.camel@snotra.buserror.net> (raw)
In-Reply-To: <1401142837010-82686.post@n7.nabble.com>
On Mon, 2014-05-26 at 15:20 -0700, shiva7 wrote:
> shiva7 wrote
> > Thanks again Scott.
> /
> >> Any idea whether the DBCR0 BRT bit actually works(??),
> >
> >> Do you have reason to believe that it might not?
> /
> >
> > I'm facing a strange problem which was not there on server processor. Let
> > me try to give brief flow.
> >
> > Server :
> >
> > Set BE bit (thru system call or sigreturn) for specific thread -> for
> > every branch -> trace exception -> Normal exception prolog
> > (STD_EXCEPTION_COMMON) SRR0 and SRR1
> >
> > Embedded/BOOKE:
> >
> > Set DE & BRT bit (thru system call or sigreturn) for specific thread ->
> > for every branch taken -> Debug exception -> DEBUG_DEBUG prolog ->
> > return_dbg_except DSRR0 & DSRR1
> >
> > In server case, able to capture the branches as expected, but wherein
> > BOOKE though branch taken exception are generated, at the certain stage
> > (mostly after turn on BRT & DE bit) user process is deviated (not taking
> > the same flow as like server) and leading to different
> > corruption/unexpected behavior.
> /
> >> And also, anything special required for "server" family application code
> >> porting here ?? as because in server family the trace exception used to
> >> viz
> >> NORMAL exception proglog and uses SRR0 and SRR1 but in this ISA/embedded
> >> case have dedicated DEBUG_DEBUG prolog and dedicated registers DSRR0 and
> >> DSRR1.
> >
> >> IIRC the branch taken mechanism does have different semantics than the
> >> equivalent mechanism on server. You can find discussion of this in the
> >> archives. :-)
> /
> >
> > Most of the discussions so far I have surfed are related to branch
> > taken/fall through(not taken) semantics related. But, in general, if I
> > have an application running on server where tracing was based on BE bit
> > and same can run on e500mc with DE & BRT combination?
> >
> >
> > Thanks In Advance.
>
> Could someone help on this regard?
I think you'll need to debug it, and send a patch if you find a bug. As
for "in general" that depends on whether your application cares about
the difference in semantics that was noted.
-Scott
next prev parent reply other threads:[~2014-05-29 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 23:21 questions on CONFIG_PPC_ADV_DEBUG_REGS, DBCR0_BRT, and DBCR0_ACTIVE_EVENTS Chris Friesen
2014-04-22 12:43 ` shiva7
2014-04-22 22:31 ` Scott Wood
2014-04-22 22:37 ` Scott Wood
2014-05-18 23:38 ` shiva7
2014-05-19 17:47 ` Scott Wood
2014-05-20 13:06 ` shiva7
2014-05-26 22:20 ` shiva7
2014-05-29 21:08 ` Scott Wood [this message]
2014-05-20 8:09 ` Deepak Pandian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401397708.6603.182.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sivasakthi7@outlook$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox