From: Pekka Paalanen <pq@iki.fi>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Christoph Hellwig" <hch@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86: explicit call to mmiotrace in do_page_fault()
Date: Sat, 9 Feb 2008 21:11:55 +0200 [thread overview]
Message-ID: <20080209211155.1dd8dc3b@daedalus.pq.iki.fi> (raw)
In-Reply-To: <84144f020802091056hffc22eckbda461534e3a6072@mail.gmail.com>
On Sat, 9 Feb 2008 20:56:07 +0200
"Pekka Enberg" <penberg@cs.helsinki.fi> wrote:
> Hi Pekka,
>
> On Feb 9, 2008 8:23 PM, Pekka Paalanen <pq@iki.fi> wrote:
> > By default it reserves 32 MB/cpu of relay buffers during module init.
> > It's this big based on experimentation with the nvidia proprietary driver.
> > There is no other way than unloading the module to free the buffers, or
> > even to clear them. This means that every time you start the user space
> > logger application, it gets old data first. Also poking the module
> > parameters via /sys is not allowed.
>
> So how is mmiotrace different from, say, blktrace that has an ioctl()
> to setup/teardown the relay channels (for mmiotrace it can be a
> "status" file that does the setup/teardown when written some
> appropriate values)?
No difference. I just have to do it at some point. I can't work on this
every day and when it comes to kernel, I'm a complete newbie. So things
will take time. If people want that I fix this before mmiotrace goes into
mainline, then so be it.
blktrace, thanks for the hint, I should take a look at that.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2008-02-09 19:12 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
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 [this message]
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=20080209211155.1dd8dc3b@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.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®