From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org, Amit Shah <amit.shah@redhat.com>,
Christoph Egger <christoph.egger@amd.com>
Subject: Re: [PATCH 2/2] add sysenter/syscall emulation for 32bit compat mode
Date: Sun, 31 May 2009 11:59:19 +0300 [thread overview]
Message-ID: <4A2246E7.7050102@redhat.com> (raw)
In-Reply-To: <1243504592-5112-2-git-send-email-andre.przywara@amd.com>
Andre Przywara wrote:
> sysenter/sysexit are not supported on AMD's 32bit compat mode, whereas
> syscall is not supported on Intel's 32bit compat mode. To allow cross
> vendor migration we emulate the missing instructions by setting up the
> processor state according to the other call.
> The sysenter code was originally sketched by Amit Shah, it was completed,
> debugged, syscall added and made-to-work by Christoph Egger and polished
> up by Andre Przywara.
> Please note that sysret does not need to be emulated, because it will be
> exectued in 64bit mode and returning to 32bit compat mode works on Intel.
> ++vcpu->stat.insn_emulation;
> if (r) {
> diff --git a/arch/x86/kvm/x86_emulate.c b/arch/x86/kvm/x86_emulate.c
> index 22c765d..41b78fa 100644
> --- a/arch/x86/kvm/x86_emulate.c
> +++ b/arch/x86/kvm/x86_emulate.c
> @@ -32,6 +32,8 @@
> #include <linux/module.h>
> #include <asm/kvm_x86_emulate.h>
>
> +#include "mmu.h"
> +
>
I think this is unneeded?
> @@ -1985,10 +1992,114 @@ twobyte_insn:
> goto cannot_emulate;
> }
> break;
> + case 0x05: { /* syscall */
> + unsigned long cr0 = ctxt->vcpu->arch.cr0;
> + struct kvm_segment cs, ss;
> +
> + memset(&cs, 0, sizeof(struct kvm_segment));
> + memset(&ss, 0, sizeof(struct kvm_segment));
> +
> + /* inject #UD if
> + * 1. we are in real mode
> + * 2. protected mode is not enabled
> + * 3. LOCK prefix is used
> + */
> + if ((ctxt->mode == X86EMUL_MODE_REAL)
> + || (!(cr0 & X86_CR0_PE))
> + || (c->lock_prefix)) {
> + /* we don't need to inject #UD here, because
> + * when emulate_instruction() returns something else
> + * than EMULATE_DONE, then svm.c:ud_interception()
> + * will do that for us.
> + */
> + goto cannot_emulate;
>
I prefer explicit injection, relying on the caller is tricky and may change.
> + case 0x07: /* sysret */
>
Since we don't emulate sysret, it should be dropped here.
> + cs.limit = 0xffffffff;
> + ss.base = 0;
> + ss.limit = 0xffffffff;
>
Once is enough.
Please move the code out of the switch and into separate functions.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-31 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 9:56 [PATCH 1/2] use explicit 64bit storage for sysenter values Andre Przywara
2009-05-28 9:56 ` [PATCH 2/2] add sysenter/syscall emulation for 32bit compat mode Andre Przywara
2009-05-31 8:59 ` Avi Kivity [this message]
2009-06-05 12:23 ` Andre Przywara
2009-06-07 7:09 ` Avi Kivity
2009-05-31 8:53 ` [PATCH 1/2] use explicit 64bit storage for sysenter values 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=4A2246E7.7050102@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=andre.przywara@amd.com \
--cc=christoph.egger@amd.com \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox