From: George Dunlap <george.dunlap@eu.citrix.com>
To: Keir Fraser <keir@xen.org>
Cc: Olaf Hering <olaf@aepfle.de>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andres Lagar-Cavilla <andreslc@gridcentric.ca>,
"Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Wait queue support for 4.3
Date: Mon, 15 Oct 2012 14:47:11 +0100 [thread overview]
Message-ID: <507C13DF.4090707@eu.citrix.com> (raw)
In-Reply-To: <CC9E2F42.4EDE2%keir@xen.org>
On 12/10/12 20:34, Keir Fraser wrote:
> On 12/10/2012 19:53, "Andres Lagar-Cavilla" <andreslc@gridcentric.ca> wrote:
>
>>> I don't see any dependency. And Tim has already proposed patches for
>>> use-case 2, in fact, as you noted. So, shouldn't they simply be polished up
>>> and applied as soon as possible? Basically, for mm type things, Tim is your
>>> man, either as author or reviewer.
>> Ok. Wanted to ascertain where we stand on things.
>>
>> Tim's patches crash guests because there are all sorts of spinlocks being
>> held. That's the gist of the mm work that needs to be done. And a separate
>> discussion.
> Yes, that's a *mm* can of worms. :) Tim is the first port of call, and
> working out who actually does the work, and what work that is, will be the
> the ensuing discussion.
So does it make sense to track this on the 4.3 feature list (obviously
with "owner: ?" until that's sorted out)? Andres, would the summary
below be accurate enough?
* Waitqueues for hypervisor accesses to shared frames which fail with
-ENOMEM
owner: ?
status: First draft posted back in February, much more work to do.
-George
next prev parent reply other threads:[~2012-10-15 13:47 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
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 [this message]
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=507C13DF.4090707@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andreslc@gridcentric.ca \
--cc=keir@xen.org \
--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.