xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Fwd: [PATCH 0/18] Nested Virtualization: Overview
Date: Thu, 15 Apr 2010 15:57:40 +0100	[thread overview]
Message-ID: <C7ECE7F4.1165A%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <201004151520.31527.Christoph.Egger@amd.com>

On 15/04/2010 14:20, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> patch 03: change local_event_delivery_* to take vcpu argument.
>                   This prevents spurious xen crashes on guest shutdown/destroy
>                   with nestedhvm enabled.

Can you give an example of how this bug manifests? I don't really see how
nestedhvm would interact so unexpectedly with this rather pv-oriented
subsystem.

> patch 04: obsolete gfn_to_mfn_current and remove it.
>                   gfn_to_mfn_current is redundant to
> gfn_to_mfn(current->domain, ...)
>                   This patch reduces the size of patch 17.

This one (at least -- there may be others) needs an ack from Tim.

> patch 05: hvm_set_cr0: Allow guest to switch into paged real mode.
>                   This makes hvmloader boot when we use xen in xen.

What if we are not running a nestedhvm guest, or otherwise on a system not
supporting paged real mode? Is it wise to remove the check in that case?
Even where we *do* support nestedhvm, should all guest writes to CR0 be
allowed to bypass that check (Isn't paged real mode architecturally only
allowed to be entered via VMRUN)?

More generally, I will allow these patches to sit for a week or two to give
time for potential reviewers to digest them.

 Thanks,
 Keir

  parent reply	other threads:[~2010-04-15 14:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 13:20 Fwd: [PATCH 0/18] Nested Virtualization: Overview Christoph Egger
2010-04-15 13:39 ` Vincent Hanquez
2010-04-15 14:50   ` Christoph Egger
2010-04-15 14:51   ` Christoph Egger
2010-04-15 14:57 ` Keir Fraser [this message]
2010-04-15 15:17   ` Christoph Egger
2010-04-15 16:26     ` Keir Fraser
2010-04-15 15:25   ` Tim Deegan
2010-04-16 10:01     ` Christoph Egger
2010-04-16  9:07 ` Qing He
2010-04-16  9:32   ` Christoph Egger
2010-04-16 10:27     ` Tim Deegan
2010-04-16 17:50       ` Keir Fraser
2010-04-20  2:07         ` Dong, Eddie
2010-04-17 11:43       ` Joerg Roedel
2010-04-18 17:52         ` Keir Fraser

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=C7ECE7F4.1165A%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Christoph.Egger@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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).