From: Tim Deegan <tim@xen.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@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:46:05 +0000 [thread overview]
Message-ID: <20160119134605.GD96813@deinos.phlegethon.org> (raw)
In-Reply-To: <1453196796.6020.217.camel@citrix.com>
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.
> Are things which are defined in xen/arch/*/Rules.mk in this way
> overrideable from the old top-level .config or does one need to dive deeper
> to modify them? If it's not configurable from top-level .config today then
> I think it either needs a "depends EXPERT" or for the changelog to make a
> convincing argument why this should be made user selectable.
I'm all in favour of making this selectable -- people who don't need
the feature can avoid 7k LOC that way. :) If it's not going to be
'EXPERT' maybe we could have some console logging, either in the
none.c stubs or just at boot time, to make it more obvious why the
user's live migration/non-HAP guest doesn't work.
Cheers,
Tim.
next prev parent reply other threads:[~2016-01-19 13:46 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 [this message]
2016-01-19 13:51 ` Andrew Cooper
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=20160119134605.GD96813@deinos.phlegethon.org \
--to=tim@xen.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@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.