Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/mm] x86/mm/mtrr: Clean up mtrr_type_lookup()
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 1 Aug 2015 09:39:07 -0700
- Cc: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>, Toshi Kani <toshi.kani@xxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Peter Anvin <hpa@xxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Brian Gerst <brgerst@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, linux-mm <linux-mm@xxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>
- In-reply-to: <20150801163311.GA15356@nazgul.tnic>
On Sat, Aug 1, 2015 at 9:33 AM, Borislav Petkov <bp@xxxxxxxxx> wrote:
>
> Well, it doesn't really make sense to write-combine IO memory, does it?
Quite the reverse.
It makes no sense to write-combine normal memory (RAM), because caches
work and sane memory is always cache-coherent. So marking regular
memory write-combining is a sign of crap hardware (which admittedly
exists all too much, but hopefully goes away).
In contrast, marking MMIO memory write-combining is not a sign of crap
hardware - it's just a sign of things like frame buffers on the card
etc. Which very much wants write combining. So WC for MMIO at least
makes sense.
Yes, yes, I realize that "crap hardware" may actually be the more
common case, but still..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]