Re: [PATCH] trim memory not covered by WB MTRRs

On Mon, Jun 25, 2007 at 08:30:52PM -0700, Jesse Barnes wrote:
> Oh, and FYI I've seen new systems with a default mapping type of WB, with a 
> few uncached holes for MMIO.  That means PAT will be absolutely required on 
> those systems if we want to use WC for the framebuffer or other memory. 

Why? As long as there are still MTRRs free you could use them for 
WC even in this setup.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>

• References:
  • [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>
  • Re: [PATCH] trim memory not covered by WB MTRRs
    • From: Jesse Barnes <[email protected]>

• Prev by Date: Re: [PATCH] trim memory not covered by WB MTRRs
• Next by Date: Re: Please release a stable kernel Linux 3.0
• Previous by thread: Re: [PATCH] trim memory not covered by WB MTRRs
• Next by thread: Re: [PATCH] trim memory not covered by WB MTRRs
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]