[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization


  • To: "Su, Disheng" <disheng.su@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Mon, 08 Oct 2007 10:13:30 +0100
  • Delivery-date: Mon, 08 Oct 2007 02:09:09 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgJfbiHYf5t3raCT5qrRGbrSVAc4gAAyqLhAAD146AAAbDcpA==
  • Thread-topic: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization

On 8/10/07 09:59, "Su, Disheng" <disheng.su@xxxxxxxxx> wrote:

>> Initialisation of guest MTRR state will need to be moved to hvmloader
>> -- we do not call setvcpucontext for HVM guests any more, so the
> 
> The problem here is to initialize MTRR MSRs of both BP and AP, in order
> to make sure MTRR MSRs are the same. Can do it in hvmloader?
> Another place to do it is in ROMBIOS, but there is lack of
> AP initialization logic. So what's your opinion about it? Do it in
> hvmloader
> , ROMBIOS or other place?

The best way, although a bit of a pain to implement, would be to bring up
all APs in hvmloader, initialise them, and HLT them. Like a proper BIOS.

I wonder whether full MTRR/PAT emulation is necessary or even particularly
desirable, however. I'd like to know what scenarios you are testing where
this improves correctness or performance.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.