From: "prasad at linux dot vnet dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10065] New: Enable SystemTap translator to create modules for Hardware Breakpoint
Date: Mon, 13 Apr 2009 11:22:00 -0000 [thread overview]
Message-ID: <20090413112231.10065.prasad@linux.vnet.ibm.com> (raw)
In-kernel interfaces to use Hardware Breakpoint registers are proposed for
inclusion in Linux Kernel through the patchset seen here:
http://lkml.org/lkml/2009/4/7/72.
Hardware Breakpoint registers can trace read/write operations on kernel
variables and can be very useful in debugging data corruption issues. The
infrastructure allows the user to define a callback function invoked through the
HW Breakpoint exception handler (analogous to the kprobe handler routines) and
can typically be used to generate backtraces, data access logs, print messages, etc.
It would be a good addition to SystemTap translator when generation of HW
Breakpoint modules is enabled through its characteristic probe, something like
'probe kernel.data("kernel symbol").write'.
Sample HW Breakpoint module can be found in the patchset (patch 10/11) in the
file samples/hw_breakpoint/data_breakpoint.c
--
Summary: Enable SystemTap translator to create modules for
Hardware Breakpoint
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: prasad at linux dot vnet dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10065
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-04-13 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 11:22 prasad at linux dot vnet dot ibm dot com [this message]
2009-04-13 13:33 ` [Bug translator/10065] " fche at redhat dot com
2010-04-30 18:00 ` jistone at redhat dot com
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=20090413112231.10065.prasad@linux.vnet.ibm.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).