* [Bug kprobes/2184] New: jprobe_return() requirement should be eliminated
@ 2006-01-20 0:22 anil dot s dot keshavamurthy at intel dot com
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
0 siblings, 2 replies; 3+ messages in thread
From: anil dot s dot keshavamurthy at intel dot com @ 2006-01-20 0:22 UTC (permalink / raw)
To: systemtap
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug kprobes/2184] jprobe_return() requirement should be eliminated
2006-01-20 0:22 [Bug kprobes/2184] New: jprobe_return() requirement should be eliminated anil dot s dot keshavamurthy at intel dot com
@ 2009-04-03 17:59 ` fche at redhat dot com
2009-04-06 5:04 ` ananth at in dot ibm dot com
1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2009-04-03 17:59 UTC (permalink / raw)
To: systemtap
------- Additional Comments From fche at redhat dot com 2009-04-03 17:59 -------
Shall we CLOSE/WONTFIX this one?
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug kprobes/2184] jprobe_return() requirement should be eliminated
2006-01-20 0:22 [Bug kprobes/2184] New: jprobe_return() requirement should be eliminated anil dot s dot keshavamurthy at intel dot com
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
1 sibling, 0 replies; 3+ messages in thread
From: ananth at in dot ibm dot com @ 2009-04-06 5:04 UTC (permalink / raw)
To: systemtap
------- Additional Comments From ananth at in dot ibm dot com 2009-04-06 05:03 -------
Sure, done!
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WONTFIX
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-04-06 5:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-01-20 0:22 [Bug kprobes/2184] New: jprobe_return() requirement should be eliminated anil dot s dot keshavamurthy at intel dot com
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
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).