From: Hien Nguyen <hien@us.ibm.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: systemtap minutes 20060427 kprobes portion
Date: Thu, 27 Apr 2006 17:57:00 -0000 [thread overview]
Message-ID: <44510604.4000105@us.ibm.com> (raw)
Attendees
IBM - Ananth, Prasanna, Hien , Henry, Ryan, Jeff
Hitachi - Satoshi
User space probes -
Prasanna will post patches again next week, this time with the clear
description and usages.
Fault handling -
Regarding setjmp and longjmp handlers, kgdb folks has this code sit on
mm tree. We need to work with kgdb folks on how to add this code to the
main line.
Helps Andrew -
People have a better description and mention the level of seriousness
for the patch. We need have a clean up patche to fix all the coding styles.
Kprobes-booter -
Hitichi folks should test this patch on other architectures to make the
it does not break the build and the common code.
kretprobe (null out unsued handlers) patch is in RHEL4 U4.
reply other threads:[~2006-04-27 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44510604.4000105@us.ibm.com \
--to=hien@us.ibm.com \
--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).