From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Pavel Roskin <proski@gnu.org>, Dave Airlie <airlied@gmail.com>,
Pekka Paalanen <pq@iki.fi>,
linux-kernel@vger.kernel.org, jbeulich@novell.com
Subject: Re: Replacement for page fault notifiers?
Date: Thu, 10 Jan 2008 11:56:47 +1100 [thread overview]
Message-ID: <1199926607.6734.158.camel@pasglop> (raw)
In-Reply-To: <20080109164241.7daa5770@laptopd505.fenrus.org>
> I'm btw all in favor of making mmio tracing full fledged kernel infrastructure.
> This doesn't mean "notifier" imo; this means a real flag in the struct page,
> and then the page fault code can do
>
> if (page->flags & FLAG_MMIO_TRACED)
> mmio_trace(page, regs, whatever..);
>
> (probably surrounded by a CONFIG_ ifdef)
> THis is a TON lighter than a notifier chain, and actually what you want,
> you don't really want a notifier, you want a call back when a special kind of
> page is touched.
>
Except that MMIO has no struct page's...
Cheers,
Ben.
next prev parent reply other threads:[~2008-01-10 0:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 19:06 Replacement for page fault notifiers? Pekka Paalanen
2008-01-08 20:32 ` Christoph Hellwig
2008-01-08 22:13 ` Dave Airlie
2008-01-09 0:26 ` Benjamin Herrenschmidt
2008-01-09 18:18 ` Pavel Roskin
2008-01-09 18:21 ` Christoph Hellwig
2008-01-09 19:58 ` Benjamin Herrenschmidt
2008-01-09 20:22 ` Christoph Hellwig
2008-01-10 0:42 ` Arjan van de Ven
2008-01-10 0:47 ` Andi Kleen
2008-01-10 0:55 ` Arjan van de Ven
2008-01-10 0:58 ` Benjamin Herrenschmidt
2008-01-10 1:01 ` Andi Kleen
2008-01-10 0:56 ` Benjamin Herrenschmidt [this message]
2008-01-10 2:03 ` Matt Mackall
2008-01-10 2:21 ` Pavel Roskin
2008-01-10 2:30 ` Matt Mackall
2008-01-10 18:44 ` Pekka Paalanen
2008-01-09 20:24 ` Pavel Roskin
2008-01-09 20:26 ` Christoph Hellwig
2008-01-09 20:41 ` Pavel Roskin
2008-01-09 20:44 ` Valdis.Kletnieks
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=1199926607.6734.158.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@gmail.com \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--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 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.