From: Avi Kivity <avi@qumranet.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] Save 64-bit of the IA-32e capable sysenter MSRs
Date: Thu, 31 Jul 2008 13:07:27 +0300 [thread overview]
Message-ID: <48918EDF.5000709@qumranet.com> (raw)
In-Reply-To: <488D6ECC.2050602@suse.de>
Alexander Graf wrote:
> Hi,
>
> When transitioning from KVM to the qemu userspace, we try to get and
> push a whole bunch of MSR values, including the SYSENTER ones. While
> this is basically a good idea, qemu doesn't know anything about
> SYSENTER on x86_64, which is an additional feature only available on
> Intel CPUs and thus defines SYSENTER_EIP and SYSENTER_ESP as 32-bit
> values.
>
> Because we're saving/restoring the SYSENTER values on transitions to
> userspace and the values in env->cpu only hold 32 bits, they get
> truncated to 32-bit. The easiest way around this is to widen the
> fields to 64 bits. This should not disturb the current functionality,
> but allows us to run 32-bit code on x86_64 using VMX.
>
> As this is KVM specific for now, I'll only CC the qemu mailinglist,
> but wouldn't encourage qemu to take the patch for now, as it's not
> necessary when emulating an AMD CPU.
>
Applied, thanks. I imagine save/restore support needs updating as
well? That should go into qemuy btw since maintaining the save/restore
format across forks isn't possible.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] Save 64-bit of the IA-32e capable sysenter MSRs
Date: Thu, 31 Jul 2008 13:07:27 +0300 [thread overview]
Message-ID: <48918EDF.5000709@qumranet.com> (raw)
In-Reply-To: <488D6ECC.2050602@suse.de>
Alexander Graf wrote:
> Hi,
>
> When transitioning from KVM to the qemu userspace, we try to get and
> push a whole bunch of MSR values, including the SYSENTER ones. While
> this is basically a good idea, qemu doesn't know anything about
> SYSENTER on x86_64, which is an additional feature only available on
> Intel CPUs and thus defines SYSENTER_EIP and SYSENTER_ESP as 32-bit
> values.
>
> Because we're saving/restoring the SYSENTER values on transitions to
> userspace and the values in env->cpu only hold 32 bits, they get
> truncated to 32-bit. The easiest way around this is to widen the
> fields to 64 bits. This should not disturb the current functionality,
> but allows us to run 32-bit code on x86_64 using VMX.
>
> As this is KVM specific for now, I'll only CC the qemu mailinglist,
> but wouldn't encourage qemu to take the patch for now, as it's not
> necessary when emulating an AMD CPU.
>
Applied, thanks. I imagine save/restore support needs updating as
well? That should go into qemuy btw since maintaining the save/restore
format across forks isn't possible.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-31 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 7:01 [PATCH] Save 64-bit of the IA-32e capable sysenter MSRs Alexander Graf
2008-07-28 7:01 ` [Qemu-devel] " Alexander Graf
2008-07-31 10:07 ` Avi Kivity [this message]
2008-07-31 10:07 ` [Qemu-devel] " Avi Kivity
2008-08-01 13:57 ` Alexander Graf
2008-08-01 13:57 ` [Qemu-devel] " Alexander Graf
2008-08-10 8:54 ` Avi Kivity
2008-08-10 8:54 ` [Qemu-devel] " 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=48918EDF.5000709@qumranet.com \
--to=avi@qumranet.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.