Re: [Xen-devel] [ANNOUNCE] Third release candidates for 4.0.4 and 4.1.3

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, Jul 26, 2012 at 10:04:49AM +0000, Ren, Yongjie wrote:
> I did a testing for 4.1.3-rc3 with Linux 3.4.6 as dom0.
> I met the following 3 issues.
> (1) Can't get deep C-state status via "xenpm" command.

That might be due to the CONFIG_ACPI_PROCESSOR_AGGREGATOR being compiled
in your kernel (df88b2d96e36d9a9e325bfcd12eb45671cbbc937).
If you don't have CONFIG_ACPI_PROCESSOR_AGGREG.. as either module or built-in
can you get to lower C-states?

> (2) Can't get P-state info via "xenpm" command.

That is strange. I seem to be able to get that.
Using 4.1.3: (XEN) Latest ChangeSet: Sun Jul 22 16:39:00 2012 +0100 
23324:e89be0dedeb4

This is on i3-2100 box (MSI MS-7680/H61M-P23 (MS-7680), BIOS V17.0 03/14/2011):

cpu id               : 0
total P-states       : 16
usable P-states      : 16
current frequency    : 1600 MHz
P0                   : freq       [3100 MHz]
                       transition [00000000000000000015]
                       residency  [00000000000000000813 ms]
P1                   : freq       [3000 MHz]
                       transition [00000000000000000001]
                       residency  [00000000000000000007 ms]
P2                   : freq       [2900 MHz]
                       transition [00000000000000000001]
                       residency  [00000000000000000018 ms]
P3                   : freq       [2800 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P4                   : freq       [2700 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P5                   : freq       [2600 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P6                   : freq       [2500 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P7                   : freq       [2400 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P8                   : freq       [2300 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P9                   : freq       [2200 MHz]
                       transition [00000000000000000001]
                       residency  [00000000000000000020 ms]
P10                   : freq       [2100 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P11                   : freq       [2000 MHz]
                       transition [00000000000000000002]
                       residency  [00000000000000000015 ms]
P12                   : freq       [1900 MHz]
                       transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
P13                   : freq       [1800 MHz]
                       transition [00000000000000000001]
                       residency  [00000000000000000000 ms]
P14                   : freq       [1700 MHz]
                       transition [00000000000000000001]
                       residency  [00000000000000000000 ms]
*P15                  : freq       [1600 MHz]
                       transition [00000000000000000013]
                       residency  [00000000000000001666 ms]
.. and more

> (3) HVM S3 resume error.
> No. 1 and No. 2 exists on 4.1.3-rc3, but don't exist on latest xen-unstable 
> tree.
> No. 3 issue exists on both 4.1.3-rc3 and latest xen-unstable tree.
> CCed Konrad.
> As for the PM features, could it be the reason that xen 4.1.3 can't work very 
> well with Linux 3.4.6 as Dom0?

Could be, but in 3.4 was when the xen-acpi-processor was introduced so it 
_should_ be working.
The only thought I have for the low C-states is the acpi_pad, but nothing else.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel