RE: [Xen-devel] Problems with enabling hypervisor C and P-state control

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Yu, Ke
>Sent: Friday, October 24, 2008 11:15 AM
>> 
>> 
>> Second, when I look at the P-state output (shown below), xenpm shows
>> that the lowest P-state is only set on the first socket (this is a
>> quad-core, quad-socket system). However, I have a feeling that this
>> might be a problem with displaying the data rather than the 
>underlying
>> logic. Any ideas?
>> 
>> # xenpm | grep '*'
>> *P3                  : freq       [1599 MHz]
>> *P3                  : freq       [1599 MHz]
>> *P3                  : freq       [1599 MHz]
>> *P3                  : freq       [1599 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>> *P0                  : freq       [2398 MHz]
>
>This seems a bug. From the above info, I can not decided if it 
>is xenpm issue or xen cpufreq issue. could you please provide 
>more info, e.g.
>- xen boot log (with loglvl=info), so that we can see if 
>cpufreq driver is initialized in all cpus
>- xentrace date on Px state, so that we can see if the Px 
>transition really happened.
>

BTW, did you create any domains and run any workloads?

Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel