From: Arjan van de Ven <arjan@infradead.org>
To: Pekka Paalanen <pq@iki.fi>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
"Jan Beulich" <jbeulich@novell.com>,
pq@iki.fi
Subject: Re: [PATCH] x86: Add a list for custom page fault handlers.
Date: Wed, 30 Jan 2008 10:20:47 -0800 [thread overview]
Message-ID: <20080130102047.59aae047@laptopd505.fenrus.org> (raw)
In-Reply-To: <20080127185238.4bcac54b@daedalus.pq.iki.fi>
On Sun, 27 Jan 2008 18:52:38 +0200
Pekka Paalanen <pq@iki.fi> wrote:
> From: Pekka Paalanen <pq@iki.fi>
>
> Provides kernel modules a way to register custom page fault handlers.
> On every page fault, except those handled in vmalloc_fault(), this
> will call a list of registered functions. The functions may handle
> the fault and force do_page_fault() to return immediately.
>
> This functionality is similar to the now removed page fault notifiers.
> Custom page fault handlers are used by debugging and reverse
> engineering tools. Mmio-trace is one such tool and a patch to add it
> into the tree will follow.
>
> The custom page fault handlers are called from the exact same points
> in do_page_fault() as the page fault notifiers were.
to be honest I don't like this approach.
I fully would like to see mmio tracing in the kernel, but please
make the hook explicit and direct (eg call the mmio tracing function,
not some list) instead...
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2008-01-30 18:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 16:52 Pekka Paalanen
2008-01-27 17:55 ` [RFC PATCH] x86: mmiotrace - trace memory mapped IO Pekka Paalanen
2008-01-30 22:39 ` Pekka Paalanen
2008-01-27 19:29 ` [PATCH] x86: Add a list for custom page fault handlers Ingo Molnar
2008-01-27 21:03 ` Peter Zijlstra
2008-01-30 2:28 ` Harvey Harrison
2008-01-30 2:34 ` Harvey Harrison
2008-01-30 18:08 ` Pekka Paalanen
2008-01-31 15:07 ` Ingo Molnar
2008-01-31 16:02 ` [PATCH v2] " Pekka Paalanen
2008-01-31 16:15 ` Arjan van de Ven
2008-02-03 6:55 ` Pekka Paalanen
2008-02-03 7:03 ` Ingo Molnar
2008-02-03 21:40 ` Pekka Paalanen
2008-02-05 20:28 ` [PATCH 1/4] x86 mmiotrace: use lookup_address() Pekka Paalanen
2008-02-05 20:30 ` [PATCH 2/4] x86 mmiotrace: fix relay-buffer-full flag for SMP Pekka Paalanen
2008-02-05 20:44 ` Eric Dumazet
2008-02-05 21:14 ` Pekka Paalanen
2008-02-05 21:35 ` Eric Dumazet
2008-02-09 17:53 ` [PATCH] x86 mmiotrace: Use percpu instead of arrays Pekka Paalanen
2008-02-05 20:31 ` [PATCH 3/4] x86 mmiotrace: comment about user space ABI Pekka Paalanen
2008-02-05 20:39 ` [PATCH 4/4] x86 mmiotrace: move files into arch/x86/mm/ Pekka Paalanen
2008-02-06 3:02 ` Randy Dunlap
2008-02-09 11:21 ` Pekka Paalanen
2008-02-07 12:53 ` Ingo Molnar
2008-02-07 12:56 ` Christoph Hellwig
2008-02-09 17:52 ` [RFC PATCH] x86: explicit call to mmiotrace in do_page_fault() Pekka Paalanen
2008-02-09 18:01 ` Arjan van de Ven
2008-02-09 18:23 ` Pekka Paalanen
2008-02-09 18:56 ` Pekka Enberg
2008-02-09 19:11 ` Pekka Paalanen
2008-02-09 19:19 ` Pekka Enberg
2008-02-09 18:39 ` Peter Zijlstra
2008-02-09 18:39 ` Peter Zijlstra
2008-02-10 18:05 ` [RFC PATCH v2] " Pekka Paalanen
2008-02-11 2:12 ` Pavel Roskin
2008-02-11 18:04 ` Pekka Paalanen
2008-02-06 5:00 ` [PATCH 1/4] x86 mmiotrace: use lookup_address() Christoph Hellwig
2008-02-07 12:52 ` Ingo Molnar
2008-01-31 16:16 ` [RFC PATCH v2] x86: mmiotrace - trace memory mapped IO Pekka Paalanen
2008-01-31 16:29 ` Arjan van de Ven
2008-02-03 7:21 ` Pekka Paalanen
2008-01-30 18:20 ` Arjan van de Ven [this message]
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=20080130102047.59aae047@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pq@iki.fi \
/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
all inboxes | Powered by JetHome®