[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <479904DF.60305@zytor.com>
Date: Thu, 24 Jan 2008 13:36:31 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: "Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Ingo Molnar <mingo@...e.hu>,
Andreas Herrmann3 <andreas.herrmann3@....com>,
Venki Pallipadi <venkatesh.pallipadi@...el.com>, ak@....de,
rdreier@...co.com, torvalds@...ux-foundation.org, gregkh@...e.de,
airlied@...net.ie, davej@...hat.com, tglx@...utronix.de,
akpm@...ux-foundation.org, arjan@...radead.org,
jesse.barnes@...el.com, davem@...emloft.net,
linux-kernel@...r.kernel.org
Subject: Re: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes
Eric W. Biederman wrote:
>>
>> | WB WT WC UC
>> ---+---------------
>> WB | WB WT WC UC
>> WT | WT WT UC UC
>> WC | WC UC WC UC
>> UC | UC UC UC UC
>>
>> With the current PAT encoding:
>>
>> WB = 00
>> WT = 01
>> WC = 10
>> UC = 11
>>
>> ... this is simply a bitwise OR. This makes sense, since one of the bits denies
>> delaying writes (WT, UC), and the other denies delaying reads (WC, UC).
>
> Almost. There is a specific case and important where MTRR UC + page table WC == WC.
>
> But yes. For ioremap where we are WB + MTRR == MTRR we need to request the
> same attributes as the e820 map, to get the attribute checking correct.
>
True; however, that shouldn't be followed for the case of conflicting
attempts at mapping.
Now, I *believe* it is safe to have some mappings UC and some WC. This
is also something to keep in mind (there are legitimate applications for
that particular form of aliasing, too.) If so, we may not want to thump
at those.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists