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

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


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Michael A Fetterman" <Michael.Fetterman@xxxxxxxxxxxx>
  • Date: Tue, 9 Oct 2007 10:23:37 +0100
  • Cc: "Su, Disheng" <disheng.su@xxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 09 Oct 2007 02:24:17 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=h5+I7MSdCpEh263rjAd/wzZlSs8cGjQdw3Xtzmm5ZVmd4NqSicOKtBst+nlqNZBbGs2m/U1wup3QijSJLdq66lYf8k5yvWAo8eJfdjtnGZdFCYlos56Py5gN67IZS1xxC/WCRaQGRZPLeG4H/qbEbQkFamOJR3s7TWSfu2Kc9m0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> > But, yes this is really a good point. So we need to do WBINVD when VP
> > migrates (of course for pass-through domain only), while the prefered
> > approach is to pin VCPU on pCPUs.
>
> Or WBINVD all CPUs when a VCPU executes WBINVD. Or explicitly track dirty
> caches for each vCPU.

I shutter to think of allowing a guest to cause a WBINVD.

In modern systems (8M+ of cache, etc), it can take 4+ milliseconds to execute.
I dare say it could, in a worst case scenerio, be even worse if you
did it on multiple
CPUs or hyperthreads at once.  And the cpu is non-interruptable the entire time.

_______________________________________________
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®.