Re: [Xen-devel] MTRR issue introduced by c/s 17404

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

But that's an existing range that is extended, rather than a new range being
declared. So how come the MTRR code gets confused?

Anyway, its days are numbered since I plan to move it out into hvmloader.
But please send a fix for now.

 -- Keir

On 10/4/08 09:33, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:

> Due to c/s 17404 reserves one more special page in build_e820map(), MTRR
> can't cover all memory ranges. In order to fix it, need to do relevant
> changing in setup_var_mtrrs() which uses magic number to caculate size.
> It's the second time this issue occurs. It's better to get rid the magic
> number. Thanks!
> 
> Randy (Weidong) 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel