Messages in this thread | | | From | "Liu, Jinsong" <> | Subject | RE: [PATCH 1/2] Xen acpi pad implement | Date | Wed, 7 Nov 2012 13:06:46 +0000 |
| |
Shuah Khan wrote: > On Thu, Oct 25, 2012 at 6:19 AM, Liu, Jinsong <jinsong.liu@intel.com> > wrote: >> From f233ad06cf924116693d7d38be9ae9d8c11f8a9b Mon Sep 17 00:00:00 >> 2001 >> From: Liu, Jinsong <jinsong.liu@intel.com> >> Date: Fri, 26 Oct 2012 02:32:48 +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. > > "logic" instead of staff (guessing this is supposed to stuff) >
Yes.
>> 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. > hypervisor > rest of the work? - could you add more details on what is handled by > this think PAD driver and what would be left to the host pad driver.
OK, add at updated patch.
Thanks, Jinsong
| |