public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Lynch <rusty@linux.co.intel.com>
To: vamsi@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Multiple kprobes per address
Date: Fri, 8 Nov 2002 13:00:26 -0800	[thread overview]
Message-ID: <200211082100.gA8L0Q515460@linux.intel.com> (raw)

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?

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?

     -rustyl

             reply	other threads:[~2002-11-08 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08 21:00 Rusty Lynch [this message]
2002-11-11  8:05 ` Multiple kprobes per address Vamsi Krishna S .
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=200211082100.gA8L0Q515460@linux.intel.com \
    --to=rusty@linux.co.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vamsi@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