From: Keir Fraser <keir@xen.org>
To: Andres Lagar-Cavilla <andreslc@gridcentric.ca>, xen-devel@lists.xen.org
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Olaf Hering <olaf@aepfle.de>, Tim Deegan <tim@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Wait queue support for 4.3
Date: Fri, 12 Oct 2012 17:30:34 +0100 [thread overview]
Message-ID: <CC9E043A.4EDAA%keir@xen.org> (raw)
In-Reply-To: <9105FC08-5D2C-440C-A0F7-C2F2D010E899@gridcentric.ca>
On 12/10/2012 16:38, "Andres Lagar-Cavilla" <andreslc@gridcentric.ca> wrote:
> During the last Xen Summit there were informal discussions about the status of
> wait queues in the hypervisor.
>
> To recap:
> 1. Wait queues are used in mem event, when events generated by a vcpu overflow
> the ring size
> 2. We would like to use wait queues when the hypervisor needs a paged out
> frame (say for hvm_copy)
> 3. We would like to use wait queues to avoid the two decoupled mmio emulation
> passes
> 4. We would like to use wait queues when the hypervisor needs write access to
> a shared frame (say for hvm copy), and unsharing temporarily fails with
> ENOMEM.
>
> Conceivably more uses for wait queues may come down the line.
>
> Use-cases 2. and 4. were left out of the time frame of 4.2, because a vcpu
> cannot go to sleep on a wait queue while holding a spinlock, and such
> situations would frequently arise. Preliminary patches from Tim Deegan have
> floated on the list
> (http://lists.xen.org/archives/html/xen-devel/2012-02/msg02133.html). We would
> like this functionality to be present on the mm side for 4.3, and then proceed
> to remove the "thinking" that consumers of the p2m interface now need to
> perform.
>
> The current maintainer (effectively) for wait queues is Keir. Keir, any ideas
> on a schedule for the cleanup?
I maintain the wait-queue mechanism, but not every (potential) user of it!
The only use-case above that might fall into my domain is 3, I think.
-- Keir
> Thanks
> Andres
>
next prev parent reply other threads:[~2012-10-12 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:38 Wait queue support for 4.3 Andres Lagar-Cavilla
2012-10-12 16:30 ` Keir Fraser [this message]
2012-10-12 16:43 ` Andres Lagar-Cavilla
2012-10-12 17:26 ` Keir Fraser
2012-10-12 18:53 ` Andres Lagar-Cavilla
2012-10-12 19:34 ` Keir Fraser
2012-10-15 13:47 ` George Dunlap
2012-10-15 14:12 ` Andres Lagar-Cavilla
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=CC9E043A.4EDAA%keir@xen.org \
--to=keir@xen.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andreslc@gridcentric.ca \
--cc=olaf@aepfle.de \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.