|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization
> > 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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, (continued)
- RE: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Dong, Eddie
- Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Keir Fraser
- Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization,
Michael A Fetterman <=
- Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Keir Fraser
- RE: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Dong, Eddie
- Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Keir Fraser
- Re: [Xen-devel] [PATCH 0/2] MTRR/PAT virtualization, Keir Fraser
|
|
|
|
|