public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: S Vamsikrishna <vamsi_krishna@in.ibm.com>
Cc: prasanna@in.ibm.com, linux-kernel@vger.kernel.org,
	shemminger@osdl.org, suparna@in.ibm.com
Subject: Re: [0/3]kprobes-base-268-rc3.patch
Date: 9 Aug 2004 13:26:03 +0200
Date: Mon, 9 Aug 2004 13:26:03 +0200	[thread overview]
Message-ID: <20040809112603.GA25663@muc.de> (raw)
In-Reply-To: <OF3CCCD7A9.BF71DED2-ON85256EEB.0006D48C-85256EEB.000CA600@in.ibm.com>

On Sun, Aug 08, 2004 at 10:23:15PM -0400, S Vamsikrishna wrote:
> Hi,
> 
> A few comments/questions on this patch:
> 
> - An unconditional call is added in the do_page_fault hot path. Is this 
> ok? 
>   The version of kprobes that hooks directly into the do_page_fault is 
> better
>   in the common case of page fault occuring outside of the kprobe handler,
>   the overhead is only a global variable load and compare. 

If this should be a problem the notifier can be changed again to do
a quick check inline if the notifier list is empty or not.

The old notifiers were fully inline, but that was changed later.

> 
> - Would the absence of any locking on the read-side of the notifier chains
>   cause any problems, especially when it is in a frequently hit place
>   like the do_page_fault?

The notifiers were intended to not be unloaded originally. But with RCU
you could unload them anyways

(ok would probably need some depends memory barriers in the notifier
walk on Alpha, should work everywhere else) 

-Andi

       reply	other threads:[~2004-08-09 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF3CCCD7A9.BF71DED2-ON85256EEB.0006D48C-85256EEB.000CA600@in.ibm.com>
2004-08-09 11:26 ` Andi Kleen [this message]
     [not found] <2pMzT-XA-21@gated-at.bofh.it>
2004-08-05 10:55 ` [0/3]kprobes-base-268-rc3.patch Andi Kleen
2004-08-06 12:37   ` [0/3]kprobes-base-268-rc3.patch Prasanna S Panchamukhi
2004-08-06 15:16     ` [0/3]kprobes-base-268-rc3.patch Andi Kleen
2004-08-06 16:31       ` [0/3]kprobes-base-268-rc3.patch Prasanna S Panchamukhi
2004-08-06 16:46         ` [0/3]kprobes-base-268-rc3.patch Andi Kleen
2004-08-07 22:37         ` [0/3]kprobes-base-268-rc3.patch Alan Cox
2004-08-06 16:37   ` [0/3]kprobes-base-268-rc3.patch Prasanna S Panchamukhi
2004-08-05  9:18 [0/3]kprobes-base-268-rc3.patch Prasanna S Panchamukhi

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=20040809112603.GA25663@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasanna@in.ibm.com \
    --cc=shemminger@osdl.org \
    --cc=suparna@in.ibm.com \
    --cc=vamsi_krishna@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