On Fri, 2011-03-25 at 15:08 +0100, Michael Kuron wrote:
> > > cpufreq=dom0-kernel
> >
> > Oh, I wasn't aware that was an option. But as the note says, it only
> > works if you set a 1-to-1 mapping between physical CPUs and vCPUs in
> > dom0.
>
> The 1-to-1 mapping is set using the dom0_vcpu_pin option, which is
> implied by the cpufreq=dom0-kernel option (taken from
> xen-4.0.1/xen/common/domain.c:setup_cpufreq_option):
> if ( !strcmp(str, "dom0-kernel") )
> {
> xen_processor_pmbits &= ~XEN_PROCESSOR_PM_PX;
> cpufreq_controller = FREQCTL_dom0_kernel;
> opt_dom0_vcpus_pin = 1;
> return;
> }
>
>
> The cpufreq=dom0-kernel option is what I am actually interested in
> because cpufreq=xen is not supported on older AMD CPUs. However, I
> have not been able to actually get it to work yet.
OK, I'm reopening the bug, but I'm afraid I'm not likely to spend time
investigating it.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part