From: "Ky Srinivasan" <ksrinivasan@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: vcpu_pause
Date: Sun, 04 Mar 2007 16:02:37 -0700 [thread overview]
Message-ID: <45EAF9DA.E57C.0030.0@novell.com> (raw)
In-Reply-To: <C2106469.337F%Keir.Fraser@cl.cam.ac.uk>
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@cl.cam.ac.uk>, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> 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@novell.com> 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@lists.xensource.com
>> http://lists.xensource.com/xen- devel
next prev parent reply other threads:[~2007-03-04 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 23:26 vcpu_pause Ky Srinivasan
2007-03-04 11:56 ` vcpu_pause Keir Fraser
2007-03-04 23:02 ` Ky Srinivasan [this message]
2007-03-05 8:09 ` vcpu_pause Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45EAF9DA.E57C.0030.0@novell.com \
--to=ksrinivasan@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.