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

[Xen-devel] Re: [PATCH 4/4] ACPI: Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen


  • To: "Wei, Gang" <gang.wei@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 03 Mar 2009 08:52:05 +0000
  • Cc:
  • Delivery-date: Tue, 03 Mar 2009 00:52:30 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcmYErlDUyweCvc1R7ySGeeN+JHq9QDEtUERAB3zCFAAD/5Ocw==
  • Thread-topic: [PATCH 4/4] ACPI: Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen

On 03/03/2009 01:23, "Wei, Gang" <gang.wei@xxxxxxxxx> wrote:

>>> Enable THERM_CONTROL MSR write for dom0 even cpufreq=xen
>>> 
>>> Signed-off-by: Wei Gang <gang.wei@xxxxxxxxx>
>> 
>> If dom0 is not the cpufreq controller then it is not pinned onto particular
>> physical CPUs and fiddling with MSRs is rather suspect.
> 
> Yes, you are right. But what we really need is simply pinning dom0 vcpus, not
> dom0 acting as cpufreq controller, am I right?
> We do expect the MSR throttling still work while xen behaves  as the cpufreq
> controller.

Then should the patch be dependent on opt_dom0_vcpus_pin?

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