All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@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:54:45 +0000	[thread overview]
Message-ID: <569E4025.7080003@citrix.com> (raw)
In-Reply-To: <1453211428.29930.44.camel@citrix.com>

On 19/01/16 13:50, Ian Campbell wrote:
>
>>> 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).

There is no requirement one way or another.  It function in any
combination you care to pick.

However, if you don't have HAP all the way down, Xen falls over very
quickly with spinlock contention if a guest actually starts doing some
real work.

~Andrew

  reply	other threads:[~2016-01-19 13:54 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 [this message]
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=569E4025.7080003@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 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.