RE: [Xen-devel] poweroff in 3.2 and 3.3

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

>From: Jan Beulich
>Sent: Thursday, November 20, 2008 4:31 PM
>
>>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 20.11.08 09:18 >>>
>>On 20/11/08 08:18, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>>
>>>> Comment says "Only s3 is using this path", instead of "this path
>>>> can only be used by s3". :-) At that time cpu online/offline is not
>>>> supported and thus only s3 is the user on that path. If you look at
>>>> latest xen upstream with cpu offline support, that comment went
>>>> away.
>>> 
>>> But my point is that this is wrong (no matter how it's 
>worded): entering
>>> S5 also uses this path, and in that case there's nothing that stops
>>> non-current vCPU-s of dom0.
>>
>>If you're powering off, why does it matter if VCPUs are paused or not?
>
>Because they can prevent the idle vCPU-s from being entered as needed
>in order to fully bring down pCPU-s. This is what a customer 
>is reporting
>(on 3.2), prompting the start of this mail thread. And I've too seen
>occasional problems with pCPU-s going down prior to power off, just not
>as bad as they do (where things end up in a panic).
>

Well, then probably we need check domains/dom0-vcpus for both, and 
then only forcefully freeze them for S5.

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