From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Doug Goldstein <cardoe@cardoe.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86: Convert shadow-paging to Kconfig
Date: Tue, 19 Jan 2016 13:50:28 +0000 [thread overview]
Message-ID: <1453211428.29930.44.camel@citrix.com> (raw)
In-Reply-To: <569E3C86.20407@citrix.com>
On Tue, 2016-01-19 at 13:39 +0000, Andrew Cooper wrote:
> On 19/01/16 09:46, 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?
>
> Not in the slightest.
>
> > What about nested virt?
>
> Nested virt is completely broken with respect to migration.
Sorry, I meant impact (generally) on nested, not WRT migration. AIUI shadow
is required for either L1 or L2 (not sure which).
> > 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?
>
> Absolutely everything anywhere in the build system is/was configurable
> from the top .config
OK, good, so no change here, that's fine then.
> > Lastly, Tim is maintainer of the shadow code and should have been CC-d,
> > also George as maintainer of the mm stuff might have an interest. Both
> > CC-s
> > added.
>
> Oops yes, although this is an entirely mechanical alteration to an
> option which already existed.
>
> ~Andrew
next prev parent reply other threads:[~2016-01-19 13:50 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 [this message]
2016-01-19 13:54 ` Andrew Cooper
2016-01-19 13:46 ` Tim Deegan
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
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=1453211428.29930.44.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@eu.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 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.