From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: Rusty Lynch <rusty@linux.co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple kprobes per address
Date: Mon, 11 Nov 2002 13:35:49 +0530 [thread overview]
Message-ID: <20021111133548.A16731@in.ibm.com> (raw)
In-Reply-To: <200211082100.gA8L0Q515460@linux.intel.com>; from rusty@linux.co.intel.com on Fri, Nov 08, 2002 at 01:00:26PM -0800
Hi,
On Fri, Nov 08, 2002 at 01:00:26PM -0800, Rusty Lynch wrote:
> I noticed that kprobes is designed around the idea of only allowing
> a single probe point per probe address. Why not allow multiple probe
> points for a given probe address? Is it a way of limiting complexity?
>
We didn't think it would be useful and conceptually, it is simpler to
think of one probe at an address.
> It looks like it would be fairly straight forward to change get_kprobe(addr)
> to be get_kprobes(addr) where it returns a list of probe points associated
> with the address, and then tweak do_int3 to work through the entire list.
> Would such a change be acceptable?
>
It will be trivial to add this, but why? Is there a good reason
for wanting to do this (multiple kprobes at same address) as opposed
to doing all you want done on a probe hit in a single handler?
Regards,
Vamsi.
--
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com
next prev parent reply other threads:[~2002-11-11 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 21:00 Multiple kprobes per address Rusty Lynch
2002-11-11 8:05 ` Vamsi Krishna S . [this message]
2002-11-11 18:35 ` Rusty Lynch
2002-11-12 8:33 ` Vamsi Krishna S .
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=20021111133548.A16731@in.ibm.com \
--to=vamsi@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linux.co.intel.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