From: Joerg Roedel <joro@8bytes.org>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 2/2] KVM: x86 emulator: Drop EFER.SVME requirement from VMMCALL
Date: Tue, 5 Apr 2011 15:41:44 +0200 [thread overview]
Message-ID: <20110405134144.GA19819@8bytes.org> (raw)
In-Reply-To: <1302010111-23431-3-git-send-email-avi@redhat.com>
On Tue, Apr 05, 2011 at 04:28:31PM +0300, Avi Kivity wrote:
> VMMCALL requires EFER.SVME to be enabled in the host, not in the guest, which
> is what check_svme() checks.
Well, yes and no. The guest has no dedicated EFER. EFER is switched in
VMRUN which is why SVME must be set in the VMCBs EFER. This value makes
it into the arch.efer too with Nested-SVM.
According to the documentation VMMCALL throws an #UD if SVME is 0 which
is why I added the check. On the other hand, at host-level it throws
always an #UD and in the guest EFER.SVME is always enabled, so the check
doesn't really make sense. I just added it because is is documented.
Joerg
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> arch/x86/kvm/emulate.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index a77c8f6..4aa5d65 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -2677,7 +2677,7 @@ static struct opcode group7_rm1[] = {
>
> static struct opcode group7_rm3[] = {
> DIP(SrcNone | ModRM | Prot | Priv, vmrun, check_svme_pa),
> - DIP(SrcNone | ModRM | Prot | VendorSpecific, vmmcall, check_svme),
> + DI(SrcNone | ModRM | Prot | VendorSpecific, vmmcall),
> DIP(SrcNone | ModRM | Prot | Priv, vmload, check_svme_pa),
> DIP(SrcNone | ModRM | Prot | Priv, vmsave, check_svme_pa),
> DIP(SrcNone | ModRM | Prot | Priv, stgi, check_svme),
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-05 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 13:28 [PATCH 0/2] Fix a couple of bugs in VMMCALL Avi Kivity
2011-04-05 13:28 ` [PATCH 1/2] KVM: x86 emulator: Re-add VendorSpecific tag to VMMCALL insn Avi Kivity
2011-04-05 13:28 ` [PATCH 2/2] KVM: x86 emulator: Drop EFER.SVME requirement from VMMCALL Avi Kivity
2011-04-05 13:41 ` Joerg Roedel [this message]
2011-04-05 16:18 ` Avi Kivity
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=20110405134144.GA19819@8bytes.org \
--to=joro@8bytes.org \
--cc=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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