From: "Abhishek Sagar" <sagar.abhishek@gmail.com>
To: "Jim Keniston" <jkenisto@us.ibm.com>
Cc: "Srinivasa Ds" <srinivasa@in.ibm.com>,
linux-kernel@vger.kernel.org, prasanna@in.ibm.com,
davem@davemloft.net, anil.s.keshavamurthy@intel.com,
"Ananth N Mavinakayanahalli" <ananth@in.ibm.com>
Subject: Re: [PATCH][RFC] kprobes: Add user entry-handler in kretprobes
Date: Thu, 15 Nov 2007 20:30:13 +0530 [thread overview]
Message-ID: <863e9df20711150700i3c84374ava108f5b585e8498b@mail.gmail.com> (raw)
In-Reply-To: <1195080664.5781.78.camel@dyn9047018096.beaverton.ibm.com>
On Nov 15, 2007 4:21 AM, Jim Keniston <jkenisto@us.ibm.com> wrote:
> 2. Simplify the task of correlating data (e.g., timestamps) between
> function entry and function return.
Would adding of data and len fields in ri help? Instead of "pouching"
data in one go at registration time, this would let user handlers do
the allocation and allow them to use different kinds of data
structures per-instance.
- Abhishek Sagar
next prev parent reply other threads:[~2007-11-15 15:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47389BEB.1000901@gmail.com>
2007-11-12 18:39 ` Abhishek Sagar
2007-11-13 10:47 ` Abhishek Sagar
2007-11-14 7:57 ` Srinivasa Ds
2007-11-14 8:49 ` Abhishek Sagar
2007-11-14 10:23 ` Srinivasa Ds
2007-11-14 13:30 ` Abhishek Sagar
2007-11-14 22:51 ` Jim Keniston
2007-11-15 13:16 ` Abhishek Sagar
2007-11-15 21:16 ` Jim Keniston
2007-11-16 17:50 ` Abhishek Sagar
2007-11-17 0:54 ` Jim Keniston
2007-11-17 18:15 ` Abhishek Sagar
2007-11-19 12:26 ` Abhishek Sagar
2007-11-21 5:55 ` Jim Keniston
2007-11-21 10:20 ` Abhishek Sagar
2007-11-27 0:54 ` Jim Keniston
2007-11-15 15:00 ` Abhishek Sagar [this message]
2007-11-16 0:07 ` Jim Keniston
2007-11-16 18:53 ` Abhishek Sagar
2007-11-16 23:09 ` Jim Keniston
2007-11-17 17:09 ` Abhishek Sagar
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=863e9df20711150700i3c84374ava108f5b585e8498b@mail.gmail.com \
--to=sagar.abhishek@gmail.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=srinivasa@in.ibm.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
all inboxes | Powered by JetHome®