On Thu, May 1, 2008 at 2:26 PM, H. Peter Anvin <hpa@zytor.com> wrote:
quoted text
> Yinghai Lu wrote:
>
> >
> > >
> > > >
> > > >
> > >  Yes, 16 GB systems are already mainstream; 32 GB is common, so I don't
> see
> > > any reason to stop at 2 GB.  Instead, it should loop up to the physical
> > > address size.
> > >
> >
> > but our objective is that has 0xd0000000-0xe0000000 (WC) not to be
> > overlapping with other MTRR entries (UC)..
> >
> >
>
>  So, pray tell, how comes this algorithm can come up with a non-solution to
> the problem presented to it?
>
>  Overall, I'm feeling there is something really completely wrong if this
> needs manual tunables of any sort.

the problem is BIOS set MTRR like BIG WB - SOME SAMLL UC to spare mtrr regs.

but later X server driver want to set some range to WC. that already
is fallen in UC...

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