All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Deegan <Tim.Deegan@citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 10/14] Nested Virtualization: svm specific implementation
Date: Tue, 17 Aug 2010 17:57:55 +0100	[thread overview]
Message-ID: <20100817165755.GD20252@whitby.uk.xensource.com> (raw)
In-Reply-To: <201008171749.55377.Christoph.Egger@amd.com>

At 16:49 +0100 on 17 Aug (1282063795), Christoph Egger wrote:
> > Can you explain why we shouldn't sync the vTPR and the vlapic state when
> > the guest is in nested mode?
> 
> When the vcpu is in guest mode then v->arch.hvm_svm.vmcb->vintr.fields.tpr
> represents the tpr of the l2 guest. The l2 guest is not allowed to touch the
> l1 guest's vTPR.

Hmmm.  I'm not sure I understand exactly what the hardware vTPR should
contain when the L2 is running; I'll have to think back about exactly
what the sync of vtpr <-> vlapic means and whether the L2 guest can
cause surprising things to happen by setting the vTPR.

Tim.

-- 
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

  reply	other threads:[~2010-08-17 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 15:04 [PATCH 10/14] Nested Virtualization: svm specific implementation Christoph Egger
2010-08-09 12:57 ` Tim Deegan
2010-08-17 15:49   ` Christoph Egger
2010-08-17 16:57     ` Tim Deegan [this message]
2010-08-18  7:48       ` Christoph Egger
2010-08-18 10:45         ` Tim Deegan
2010-08-18 10:54           ` Christoph Egger

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=20100817165755.GD20252@whitby.uk.xensource.com \
    --to=tim.deegan@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 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.