From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: systemtap@sourceware.org
Subject: Re: [RFC] Hardware Breakpoint support for systemtap translator
Date: Fri, 24 Jul 2009 12:22:00 -0000 [thread overview]
Message-ID: <4A69A781.9060301@linux.vnet.ibm.com> (raw)
In-Reply-To: <4A699A1C.6080205@linux.vnet.ibm.com>
Prerna Saxena wrote:
> Hi,
> The attached set patches enable systemtap translator to probe kernel
> hardware breakpoints on x86.
> It introduces the following language constructs :
>
> 1. probe kernel.data(ADDRESS).write {....} : To probe writes at
> the given address
> 2. probe kernel.data(ADDRESS).rw {....} : To probe read &
> write access to the given address.
> 3. probe kernel.data("SYMBOL").write {....}
> 4. probe kernel.data("SYMBOL").rw {....} : Similar to 1,2, but
> using a symbol name as argument.
>
> These are agnostic to dwarf/debuginfo and depend on the hardware
> breakpoint infrastructure for resolving symbols.
>
> Things that remain to be done :
> 1. Translator support for probing hardware breakpoints on other
> architectures (ppc/s390 etc)
> 2. Implementation of userspace hardware breakpoints.
>
> I'm still testing it...Looking for comments and feedback :-)
>
Forgot to mention that the underlying kernel infrastructure is in -tip.
Would advise ppl to try these patches on systems running -tip kernel
only :-)
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2009-07-24 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 11:25 Prerna Saxena
2009-07-24 12:22 ` Prerna Saxena [this message]
2009-07-24 15:08 ` Frank Ch. Eigler
2009-07-30 11:38 ` Prerna Saxena
2009-07-24 21:12 ` Roland McGrath
2009-07-31 12:43 ` Prerna Saxena
2009-08-02 21:19 ` 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=4A69A781.9060301@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.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).