From: Pavel Roskin <proski@gnu.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.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: Wed, 09 Jan 2008 21:21:33 -0500 [thread overview]
Message-ID: <1199931693.21499.11.camel@dv> (raw)
In-Reply-To: <1199930590.6245.104.camel@cinder.waste.org>
On Wed, 2008-01-09 at 20:03 -0600, Matt Mackall wrote:
> That makes it way too easy for drivers of questionable legality to just
> clear that bit. Also, we've got a shortage of page bits, etc.
If we ever have this problem, the bit can be changed in the kernel to
fool those drivers (I hope the shortage is not so dire that there will
be no more bits left).
I don't think evil drivers should be a problem per se. There are
existing non-free drivers that still need to be traced over and over
again. I guess ndiswrapper could use tracing for Windows drivers that
don't know anything about Linux page flags.
Last but not least, mmiotrace should be useful for free drivers in the
first place to have a legitimate reason to be in the kernel.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-01-10 2:21 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
2008-01-10 2:03 ` Matt Mackall
2008-01-10 2:21 ` Pavel Roskin [this message]
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=1199931693.21499.11.camel@dv \
--to=proski@gnu.org \
--cc=airlied@gmail.com \
--cc=arjan@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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