From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386, x86_64 Initial PAT implementation
Date: Tue, 30 Aug 2005 10:06:07 -0600 [thread overview]
Message-ID: <m1r7cbpfyo.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200508301748.50941.ak@suse.de> (Andi Kleen's message of "Tue, 30 Aug 2005 17:48:50 +0200")
Andi Kleen <ak@suse.de> writes:
> On Tuesday 30 August 2005 17:20, Eric W. Biederman wrote:
>
>> Right. To the best of my understanding problem aliases are either
>> uncached/write-back or write-combine/write-back. I don't think
>> uncached/write-combine can cause problems. My basic reason for
>
> Well it can if one driver expects the mapping to be uncached and the
> other to be WC. The WC one might blast over the other one badly.
>
> Also the architecture defines all attribute conflicts to be undefined
> and it's better to not rely on undefined behaviour because that could
> break quite badly on a future microarchitecture.
Agreed. It is better.
My assessment was only to show that the immediate danger of data
corruption or problems isn't very high, even if someone does goof.
Eric
next prev parent reply other threads:[~2005-08-30 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 0:20 [PATCH] i386, x86_64 Initial PAT implementation Eric W. Biederman
[not found] ` <200508300230.39844.ak@suse.de>
2005-08-30 1:49 ` Eric W. Biederman
[not found] ` <200508300412.55027.ak@suse.de>
2005-08-30 6:21 ` solving page table access attribute aliasing Eric W. Biederman
[not found] ` <200508301714.35017.ak@suse.de>
2005-08-30 15:50 ` Eric W. Biederman
2005-08-30 14:45 ` [PATCH] i386, x86_64 Initial PAT implementation Alan Cox
2005-08-30 14:50 ` Andi Kleen
2005-08-30 15:31 ` Mikael Pettersson
2005-08-30 16:01 ` Eric W. Biederman
2005-08-30 15:20 ` Eric W. Biederman
[not found] ` <200508301748.50941.ak@suse.de>
2005-08-30 16:06 ` Eric W. Biederman [this message]
2005-08-30 17:06 ` Dave Jones
2005-08-31 1:39 ` Eric W. Biederman
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=m1r7cbpfyo.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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