public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Prasanna S Panchamukhi <prasanna@in.ibm.com>
To: bibo dot mao at intel dot com <sourceware-bugzilla@sourceware.org>
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug kprobes/2476] Switch Kprobes inline functions to __kprobes?
Date: Mon, 10 Apr 2006 04:30:00 -0000	[thread overview]
Message-ID: <20060410043031.GA28587@in.ibm.com> (raw)
In-Reply-To: <20060410032409.9593.qmail@sourceware.org>

On Mon, Apr 10, 2006 at 03:24:09AM -0000, bibo dot mao at intel dot com wrote:
> 
> ------- Additional Comments From bibo dot mao at intel dot com  2006-04-10 03:24 -------
> This patch works my IA64 box, but I have one question, almost all function in 
> arch/i386/kernel/kprobe.c is prefixed with __kprobes. currently I think that 
> the whole kernel path for KPROBE_REENTER routine should not be probed, and I do 
> know whether there are other cases which should not be probed also.

True, apart from KPROBE_REENTER, probes on routines from interrupt
handler to the kprobes_handler() can cause recursion.

Thanks
Prasanna
-- 
Prasanna S Panchamukhi
Linux Technology Center
India Software Labs, IBM Bangalore
Email: prasanna@in.ibm.com
Ph: 91-80-51776329

  reply	other threads:[~2006-04-10  4:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  0:45 [Bug kprobes/2476] New: " jkenisto at us dot ibm dot com
2006-03-23  4:56 ` [Bug kprobes/2476] " prasanna at in dot ibm dot com
2006-03-25  9:51 ` prasanna at in dot ibm dot com
2006-04-07 14:12 ` prasanna at in dot ibm dot com
2006-04-07 14:14 ` prasanna at in dot ibm dot com
2006-04-08  7:43 ` prasanna at in dot ibm dot com
2006-04-10  3:24 ` bibo dot mao at intel dot com
2006-04-10  4:30   ` Prasanna S Panchamukhi [this message]
2006-04-10  4:30 ` prasanna at in dot ibm dot com
2006-04-13 16:16 ` prasanna at in dot ibm dot com

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=20060410043031.GA28587@in.ibm.com \
    --to=prasanna@in.ibm.com \
    --cc=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).