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

RE: [Xen-devel] cpufreq status information

>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: 2008年9月8日 22:01
>On 8/9/08 14:50, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
>>> The intent is to expose the frequency of the pCPU the 
>particular vCPU
>>> is currently running on, perhaps only in Dom0.
>> Then you have to pin dom0 vCPU to corresponding pCPU, and have
>> dom0 with same number as pCPU. I don't think such limitation
>> necessary for just retrieving some pCPU information.
>> Or if you still enable vcpu migration, you have to fake virtual freq
>> change notification within dom0 at vcpu migration as pCPU may
>> scale its own freq individually.
>Greater virtualisation of cpufreq info (making it available to 
>guests, with pcpu->vcpu remapping) is just not very useful in 
>my opinion.
>It's one of those features that more hacker-ish users might 
>think they want
>to decorate their desktop.


>After all, guest performance is at least as affected by CPU (and other
>resources) contention from other guests as it is by power-management
>governors in the hyeprvisor. Indeed, if the governors are 
>doing their job
>right then guest performance should not be considerably 
>impacted by them
>even in absolute terms.

Exactly. :-)


Xen-devel mailing list



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