From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>, Ian Campbell <ian.campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: Convert shadow-paging to Kconfig
Date: Tue, 19 Jan 2016 13:51:33 +0000 [thread overview]
Message-ID: <569E3F65.2020003@citrix.com> (raw)
In-Reply-To: <20160119134605.GD96813@deinos.phlegethon.org>
On 19/01/16 13:46, Tim Deegan wrote:
> At 09:46 +0000 on 19 Jan (1453196796), Ian Campbell wrote:
>> On Mon, 2016-01-18 at 18:40 +0000, Andrew Cooper wrote:
>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> Does this have any impact on migration of either PV or HVM guests? What
>> about nested virt?
> Without shadow paging you can't do live migration of PV guests. That
> should go in the kconfig description.
>
> AFAICT nested virt depends on HAP rather than shadow.
Nothing currently enforces this. Xen dies particularly quickly with
spinlock contention if a shadow HVM guest tries to use nested-virt.
(Just another item on the long list of tasks requires before nested-virt
becomes anything other than experimental.)
~Andrew
next prev parent reply other threads:[~2016-01-19 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:40 [PATCH] x86: Convert shadow-paging to Kconfig Andrew Cooper
2016-01-18 22:53 ` Doug Goldstein
2016-01-19 9:46 ` Ian Campbell
2016-01-19 13:23 ` Jan Beulich
2016-01-19 13:30 ` Andrew Cooper
2016-01-19 13:38 ` Jan Beulich
2016-01-19 13:47 ` Andrew Cooper
2016-01-19 13:39 ` Andrew Cooper
2016-01-19 13:50 ` Ian Campbell
2016-01-19 13:54 ` Andrew Cooper
2016-01-19 13:46 ` Tim Deegan
2016-01-19 13:51 ` Andrew Cooper [this message]
2016-01-19 13:27 ` Jan Beulich
2016-01-19 13:33 ` Andrew Cooper
2016-01-19 13:39 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2016-01-29 18:20 Andrew Cooper
2016-01-29 21:46 ` Doug Goldstein
2016-02-01 9:54 ` Tim Deegan
2016-02-02 11:39 ` George Dunlap
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=569E3F65.2020003@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).