From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/13489] support upstream inode-based uprobes
Date: Wed, 20 Jun 2012 19:51:00 -0000 [thread overview]
Message-ID: <bug-13489-6586-vJSMWIupVN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13489-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13489
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |dsmith at redhat dot com
Resolution| |FIXED
--- Comment #3 from David Smith <dsmith at redhat dot com> 2012-06-20 19:50:57 UTC ---
As Josh mentioned in comment #2, finding a sleepy context was the main holdup
here. Kernels >= 3.5 have a feature called "task_work" that we're now using to
provide that sleepy context.
There are still missing features when compared to the old utrace-based uprobes
(like uretprobes), but we now support the upstream inode-based uprobes. Any
remaining bugs in the new inode-based uprobes support we can track separately.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2012-06-20 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 23:22 [Bug uprobes/13489] New: " jistone at redhat dot com
2011-12-09 23:43 ` [Bug uprobes/13489] " jistone at redhat dot com
2011-12-10 14:27 ` jistone at redhat dot com
2012-06-20 19:51 ` dsmith at redhat dot com [this message]
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=bug-13489-6586-vJSMWIupVN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).