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

Re: [Xen-devel] [PATCH 1/2] Xen acpi pad implement

>>> On 03.11.12 at 13:16, "Liu, Jinsong" <jinsong.liu@xxxxxxxxx> wrote:
> Konrad Rzeszutek Wilk wrote:
>>>> From f514b97628945cfac00efb0d456f133d44754c9d Mon Sep 17 00:00:00
>>>> 2001 
>>> From: Liu, Jinsong <jinsong.liu@xxxxxxxxx>
>>> Date: Thu, 1 Nov 2012 21:02:36 +0800
>>> Subject: [PATCH 1/2] Xen acpi pad implement
>>> PAD is acpi Processor Aggregator Device which provides a control
>>> point 
>>> that enables the platform to perform specific processor configuration
>>> and control that applies to all processors in the platform.
>>> This patch is to implement Xen acpi pad logic. When running under Xen
>>> virt platform, native pad driver would not work. Instead Xen pad
>>> driver, 
>>> a self-contained and very thin logic level, would take over acpi pad
>>> staff. When acpi pad notify OSPM, xen pad logic intercept and parse
>>> _PUR object 
>>> and then hypercall to hyervisor for the rest work, say, core parking.
>> Two comments:
>>  - Did you look at the SuSE tree? Jan mentioned that they did some
>>    fixes? Did you carry them over?
> I didn't look at Suse tree.
> Jan, would you please tell me where can I pull Suse tree?


> have you 
> implemented xen-acpi-pad logic at Suse dom0 and which points you have fixed?

Yes, we've been carrying this for quite some time. I don't recall
the specific cleanups to the code I did, so I can only refer you
to the trees above.


Xen-devel mailing list



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