public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Roland McGrath <roland@redhat.com>
Cc: Prerna Saxena <prerna@linux.vnet.ibm.com>,
	        "Frank Ch. Eigler" <fche@redhat.com>,
	systemtap@sourceware.org
Subject: Re: [RFC] Systemtap translator support for hardware breakpoints on
Date: Sat, 09 Jan 2010 00:54:00 -0000	[thread overview]
Message-ID: <20100109005428.GA3486@in.ibm.com> (raw)
In-Reply-To: <20100108185231.75F6713FE8@magilla.sf.frob.com>

On Fri, Jan 08, 2010 at 10:52:31AM -0800, Roland McGrath wrote:
> > For ppc, any length upto 8 is acceptable. IIRC, the hwbkpt kernel API 
> > takes care of filtering a hit if the defined hwbkpt probe has a separate 
> > address interval and the hit is at an address which is outside that 
> > interval. (I need to check its implementation with hw breakpoint kernel 
> > API).
> 
> I don't understand.  Do you mean that the trap handler gets the precise
> address of the load/store, not just the address aligned to 8?
>

Yes, we put the Data Address Register (DAR) to use here and know the
exact address which was accessed to cause the breakpoint exception. The
value of DAR along with the length of the symbol (taken as input from
the user when registering a breakpoint request) is used to filter out
extraneous breakpoint exceptions.

For instance, a breakpoint request for a symbol with length for 4 bytes
is accepted (anything <= 8 is considered valid). Whenever a breakpoint
exception arises, the hw_breakpoint_handler() checks to see if the value
of DAR lies between the bp_addr and bp_addr+len. If yes, we know that
the exception is a result of a memory access in the address-range we're
interested in, otherwise it returns early.

Thanks,
K.Prasad

  reply	other threads:[~2010-01-09  0:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  8:35 Prerna Saxena
2010-01-07 18:01 ` Frank Ch. Eigler
2010-01-07 21:57   ` Roland McGrath
2010-01-07 22:39     ` Roland McGrath
2010-01-07 22:45       ` Frank Ch. Eigler
2010-01-08  5:01       ` Ananth N Mavinakayanahalli
2010-01-08 10:24         ` Roland McGrath
2010-01-09  1:29           ` K.Prasad
2010-01-09  1:56             ` Roland McGrath
2010-01-08 14:35   ` [RFC] Systemtap translator support for hw breakpoints on x86 Prerna Saxena
2010-01-08 15:21     ` Frank Ch. Eigler
2010-01-09  1:41       ` K.Prasad
2010-01-25 19:00   ` [RFC V2] Systemtap translator support for kernel hardware breakpoints Prerna Saxena
2010-01-26 21:16     ` Frank Ch. Eigler
2010-01-27 15:55       ` Prerna Saxena
2010-01-27 17:12         ` Frank Ch. Eigler
2010-01-28  9:59           ` Prerna Saxena
2010-01-29  9:15             ` Prerna Saxena
2010-01-07 23:15 ` [RFC] Systemtap translator support for hardware breakpoints on Roland McGrath
2010-01-08  1:03   ` Frank Ch. Eigler
2010-01-08  1:28     ` Roland McGrath
2010-01-08  1:19 ` Roland McGrath
2010-01-08  1:53 ` Roland McGrath
2010-01-08 16:08   ` Prerna Saxena
2010-01-08 18:52     ` Roland McGrath
2010-01-09  0:54       ` K.Prasad [this message]
2010-01-09  1:07         ` Roland McGrath
2010-01-09  1:11   ` K.Prasad
2010-01-09  1:45     ` Roland McGrath
2010-01-09  2:46       ` K.Prasad
2010-01-10 21:37         ` Roland McGrath

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=20100109005428.GA3486@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=fche@redhat.com \
    --cc=prerna@linux.vnet.ibm.com \
    --cc=roland@redhat.com \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).