From: Andi Kleen <ak@suse.de>
To: Pekka Paalanen <pq@iki.fi>
Cc: Ingo Molnar <mingo@elte.hu>, David Miller <davem@davemloft.net>,
hch@lst.de, airlied@linux.ie, akpm@linux-foundation.org,
torvalds@linux-foundation.org, jbeulich@novell.com,
linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Masami Hiramatsu <mhiramat@redhat.com>
Subject: Re: [PATCH] Revert "x86: optimize page faults like all other achitectures and kill notifier cruft"
Date: Wed, 9 Jan 2008 21:08:26 +0100 [thread overview]
Message-ID: <200801092108.26550.ak@suse.de> (raw)
In-Reply-To: <20080109220148.5caebaf1@daedalus.pq.iki.fi>
> I have been reading about kprobes and one thing particularly bothers me
> in the case of mmio-trace. The probe will actually service the page
> fault, therefore it should be able force do_page_fault() to return at
> the probe point. I could not figure out a way to do that.
>
> Is it possible to do reliably with kprobes or markers?
Probes are generally not designed to change the flow of the
underlying code.
While it's in theory possible it will be always unreliable.
For checks that result in logic changes you'll always need
some kind of explicit hook.
-Andi
next prev parent reply other threads:[~2008-01-09 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 2:34 [PATCH] Revert "x86: optimize page faults like all other achitectures and kill notifier cruft" Dave Airlie
2008-01-09 2:37 ` Andi Kleen
2008-01-09 3:06 ` Andrew Morton
2008-01-09 3:17 ` Dave Airlie
2008-01-09 3:29 ` Andrew Morton
2008-01-09 3:55 ` Dave Airlie
2008-01-09 7:19 ` Christoph Hellwig
2008-01-09 7:23 ` David Miller
2008-01-09 10:41 ` Ingo Molnar
2008-01-09 16:52 ` Mathieu Desnoyers
2008-01-09 19:07 ` Andi Kleen
2008-01-09 20:01 ` Pekka Paalanen
2008-01-09 20:08 ` Andi Kleen [this message]
2008-01-09 4:17 ` Andi Kleen
2008-01-09 9:12 ` Jan Beulich
2008-01-09 15:18 ` Arjan van de Ven
2008-01-09 15:21 ` Andi Kleen
2008-01-09 15:26 ` Ingo Molnar
2008-01-09 7:17 ` Christoph Hellwig
2008-01-09 7:22 ` David Miller
2008-01-09 13:19 ` Jiri Kosina
2008-01-09 13:48 ` David Miller
2008-01-09 14:23 ` Andi Kleen
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=200801092108.26550.ak@suse.de \
--to=ak@suse.de \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=pq@iki.fi \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.