From: "anil dot s dot keshavamurthy at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2184] New: jprobe_return() requirement should be eliminated
Date: Fri, 20 Jan 2006 00:22:00 -0000 [thread overview]
Message-ID: <20060120002236.2184.anil.s.keshavamurthy@intel.com> (raw)
In the current design their is a requirement that the
instrumented jprobe_handler must call jprobe_return()
at the end. The jprobe_return()is nothing but
executes break/int3 instruction so the control
is passed back to kprobes infrastructure.
This restriction can be eliminated, if the normal return
from jprobe_handler returns to some well known kernel function
and from where we execute a break/int3. I.e before passing
the control to instrumented jprobe_handler() the retun address
is modified to go to well known function inside the kernel and
from here we execute break/int3 their by eliminating the need for
jprobe_return() from the instrumented jprobe_handler.
This technique is implemented in IA64 and seems to be working
very well and can be done for other architecture. In IA64,
jprobe_return() is defined as
static inline void jprobe_return(void) {}.
--
Summary: jprobe_return() requirement should be eliminated
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: kprobes
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: anil dot s dot keshavamurthy at intel dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2184
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-01-20 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 0:22 anil dot s dot keshavamurthy at intel dot com [this message]
2009-04-03 17:59 ` [Bug kprobes/2184] " fche at redhat dot com
2009-04-06 5:04 ` ananth at in dot ibm 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=20060120002236.2184.anil.s.keshavamurthy@intel.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).