From: Andi Kleen <andi@firstfloor.org>
To: "Cédric Augonnet" <cedric.augonnet@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, Loic Prylli <loic@myri.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
brice@myri.com, cedric.augonnet@ens-lyon.org
Subject: Re: PAT support for i386 and x86_64
Date: Wed, 8 Aug 2007 18:00:39 +0200 [thread overview]
Message-ID: <20070808160039.GA16357@one.firstfloor.org> (raw)
In-Reply-To: <f56c1ba00708080842i1eaa00kef5071d9a1f01f04@mail.gmail.com>
On Wed, Aug 08, 2007 at 11:42:17AM -0400, Cédric Augonnet wrote:
> changing this register is absolutely not the actual issue with PAT, but
> don't
> you think such a first step is needed to avoid conflicts since people _do_
> already set that register from their driver.
Which drivers do that? Ok, I know the ATI 3d driver does, but if that
crashes the users know who is to blame.
No, I don't think we should merge a potentially data corrupting "first
step.". Even first steps have to meet some standards.
> Of course there is no problem for that being dependant on a CONFIG_PAT.
I don't think a CONFIG_DATA_CORRUPTION is a good idea.
-Andi
next prev parent reply other threads:[~2007-08-08 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 2:03 [PATCH 0/2] PAT support for i386 and x86_64 Cédric Augonnet
2007-08-07 8:30 ` Andi Kleen
2007-08-08 8:26 ` Loic Prylli
2007-08-08 10:14 ` Andi Kleen
2007-08-08 15:52 ` Cédric Augonnet
[not found] ` <f56c1ba00708080842i1eaa00kef5071d9a1f01f04@mail.gmail.com>
2007-08-08 16:00 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-07 12:34 Daniel J Blueman
2007-08-07 14:10 ` Andi Kleen
2007-08-07 15:26 ` Daniel J Blueman
2007-08-07 15:33 ` Andi Kleen
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=20070808160039.GA16357@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=brice@myri.com \
--cc=cedric.augonnet@ens-lyon.org \
--cc=cedric.augonnet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic@myri.com \
/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.