This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] vcpu_pause

To: Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] vcpu_pause
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 04 Mar 2007 11:56:25 +0000
Delivery-date: Sun, 04 Mar 2007 03:55:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45E85C62.E57C.0030.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdeVCJaYOgI48pHEdu9LwAWy6hiGQ==
Thread-topic: [Xen-devel] vcpu_pause
User-agent: Microsoft-Entourage/
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

<Prev in Thread] Current Thread [Next in Thread>