From: Ingo Molnar <mingo@elte.hu>
To: Pekka Paalanen <pq@iki.fi>
Cc: Arjan van de Ven <arjan@infradead.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
linux-kernel@vger.kernel.org, Jan Beulich <jbeulich@novell.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH v2] x86: Add a list for custom page fault handlers.
Date: Sun, 3 Feb 2008 08:03:21 +0100 [thread overview]
Message-ID: <20080203070321.GA8293@elte.hu> (raw)
In-Reply-To: <20080203085522.2b63e15b@daedalus.pq.iki.fi>
* Pekka Paalanen <pq@iki.fi> wrote:
> I have two reasons why I'd like to let it be a module:
> - it's "broken", the relay buffers are cleared on module unload
> - it's a lot easier to push updated version for testing to people
>
> Ok, the first one is just a silly excuse, but the second one is to
> avoid forcing non-developer users to patch their kernels. This is a
> much needed tool for the Nouveau project even in it's current form.
i dont think this second problem is a practical one: i've test-merged
mmiotrace two days ago into x86.git and it's holding up very well in my
testing (it has not caused a single hickup so far). It's nice optional
debug functionality and i dont see any reason why not to merge it.
a few cleanup requests:
- please make the pagefault callbacks explicit as Arjan has asked
- any reason why it lives in arch/x86/kernel/mmiotrace/? It should be a
prime-time member of arch/x86/mm/ i think.
- please make it build-in-able, not modules-only.
- [ longer-term: think about integrating pf_in.c with the x86
emulator/disassembler of KVM. ]
Ingo
next prev parent reply other threads:[~2008-02-03 7:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 16:52 [PATCH] x86: Add a list for custom page fault handlers 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 [this message]
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 ` [PATCH] x86: Add a list for custom page fault handlers Arjan van de Ven
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=20080203070321.GA8293@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=harvey.harrison@gmail.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--cc=proski@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox