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: Mon, 19 May 2014 12:47:57 -0500 [thread overview]
Message-ID: <1400521677.18239.16.camel@snotra.buserror.net> (raw)
In-Reply-To: <1400456291193-82408.post@n7.nabble.com>
On Sun, 2014-05-18 at 16:38 -0700, shiva7 wrote:
> Thanks Scott.
>
> Apologize for not quoting the old email reference.
You did it again. :-)
> I assumed the old archive content always will be in the trail.
It's in the archives (as I noted), but it's a pain to search for it
versus having relevant bits quoted.
> Any idea whether the DBCR0 BRT bit actually works(??),
Do you have reason to believe that it might not?
> if I add DBCR0 under sys_debug context call? because this code seems
> like direct porting and wondering why on first place not included under
> debug_context call.
Again, it was probably an oversight, but the people who might know for
sure are no longer reachable.
> 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. :-)
-Scott
next prev parent reply other threads:[~2014-05-19 17:48 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 [this message]
2014-05-20 13:06 ` shiva7
2014-05-26 22:20 ` shiva7
2014-05-29 21:08 ` Scott Wood
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=1400521677.18239.16.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