|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] vcpu_pause
Kier,
Sorry for not being precise in my earlier email. Within an arbitrary domain, I
was wondering how we were preventing potential deadlocks between vcpus that
were attempting to pause each other; perhaps a higher level serialization lock
could solve this problem. I was looking at using vcpu_pause to get a stable
state for a vcpu in a domu context. Is this not a sanctioned usage of
vcpu_pause.
K. Y
>>> On Sun, Mar 4, 2007 at 6:56 AM, in message
<C2106469.337F%Keir.Fraser@xxxxxxxxxxxx>, Keir Fraser
<Keir.Fraser@xxxxxxxxxxxx> wrote:
> Synchronous vcpu_pause() and domain_pause() are only used on paths
> executable in dom0 context. Hence there is no loop in the graph of
> domain- X- can- pause- domain- Y, and we'll need to maintain that asymmetry
> when
> we disaggregate dom0. For now, a BUG_ON(current- >domain != dom0) in
> vcpu_sleep_sync() would probably make things clearer.
>
> -- Keir
>
> On 2/3/07 23:26, "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx> wrote:
>
>> What are the expected entry conditions to call vcpu_pause. How do we
> guarantee
>> two vcpus don't deadlock by calling pause on each other.
>>
>> Regards,
>>
>> K. Y
>>
>>
>>
>> _______________________________________________
>> Xen- devel mailing list
>> Xen- devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen- devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|