public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: shiva7 <sivasakthi7@outlook•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: questions on CONFIG_PPC_ADV_DEBUG_REGS, DBCR0_BRT, and DBCR0_ACTIVE_EVENTS
Date: Sun, 18 May 2014 16:38:11 -0700 (PDT)	[thread overview]
Message-ID: <1400456291193-82408.post@n7.nabble.com> (raw)
In-Reply-To: <1398206224.1694.254.camel@snotra.buserror.net>

Thanks Scott.

Apologize for not quoting the old email reference. I assumed the old archive
content always will be in the trail.

Any idea whether the DBCR0 BRT bit actually works(??), 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. 

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.

I can see the debug handler already have HACK to simulate the branch taken
case and SIGTRAP to user space.

Thanks in Advance.



--
View this message in context: http://linuxppc.10917.n7.nabble.com/questions-on-CONFIG-PPC-ADV-DEBUG-REGS-DBCR0-BRT-and-DBCR0-ACTIVE-EVENTS-tp70147p82408.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

next prev parent reply	other threads:[~2014-05-18 23:38 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 [this message]
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
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=1400456291193-82408.post@n7.nabble.com \
    --to=sivasakthi7@outlook$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox