From: Ian Campbell <Ian.Campbell@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: Stubdom breakage in 4.5
Date: Wed, 4 Feb 2015 12:30:01 +0000 [thread overview]
Message-ID: <1423053001.17711.41.camel@citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0257E13AD@AMSPEX01CL01.citrite.net>
On Tue, 2015-02-03 at 14:11 +0000, Paul Durrant wrote:
> How about this as a slightly hacky solution that I think may work in both cases?
>
> If Xen finds no emulator at all for an HVM guest then it waits around
> for at least one to show up before processing an emulation request.
> Until one does it stalls the vcpu in question indefinitely, but on the
> first emulator attach (i.e. ioreq server creations) then the IO will
> always be processed, even if it doesn't match the ioreq server.
It sounds plausible to me and seems like it would probably be
backportable.
Longer term I think we still need to fix the domain creation interlock
for launching multiple qemu's, ioreq servers and any other type of
service thing we might launch (whether in a stub dom or not), at which
point we may be able to remove the above workaround too.
Ian.
next prev parent reply other threads:[~2015-02-04 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:22 Stubdom breakage in 4.5 Wei Liu
2015-02-03 13:42 ` Paul Durrant
2015-02-03 13:47 ` Ian Campbell
2015-02-03 14:00 ` Paul Durrant
2015-02-04 21:52 ` Don Slutz
2015-02-03 14:11 ` Paul Durrant
2015-02-04 12:30 ` Ian Campbell [this message]
2015-02-04 12:58 ` Paul Durrant
2015-02-04 21:42 ` Don Slutz
2015-02-05 11:04 ` Paul Durrant
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=1423053001.17711.41.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=wei.liu2@citrix.com \
--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.