From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-i386: do not read/write MSR_TSC_AUX from KVM if CPUID bit is not set
Date: Thu, 31 Mar 2016 14:56:08 +0200 [thread overview]
Message-ID: <56FD1E68.5020604@redhat.com> (raw)
In-Reply-To: <1459371583-4824-1-git-send-email-pbonzini@redhat.com>
On 03/30/16 22:59, Paolo Bonzini wrote:
> KVM does not let you read or write this MSR if the corresponding CPUID
> bit is not set. This in turn causes MSRs that come after MSR_TSC_AUX
> to be ignored by KVM_SET_MRSS.
typo: KVM_SET_MRSS / KVM_SET_MSRS
Thanks for fixing this.
Laszlo
>
> One visible symptom is that s3.flat from kvm-unit-tests fails with
> CPUs that do not have RDTSCP, because the SMBASE is not reset to
> 0x30000 after reset.
>
> Fixes: c9b8f6b6210847b4381c5b2ee172b1c7eb9985d6
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> target-i386/kvm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 87ab969..19e2d94 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -917,6 +917,9 @@ int kvm_arch_init_vcpu(CPUState *cs)
> if (env->features[FEAT_1_EDX] & CPUID_MTRR) {
> has_msr_mtrr = true;
> }
> + if (!(env->features[FEAT_8000_0001_EDX] & CPUID_EXT2_RDTSCP)) {
> + has_msr_tsc_aux = false;
> + }
>
> return 0;
> }
>
next prev parent reply other threads:[~2016-03-31 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 20:59 [Qemu-devel] [PATCH] target-i386: do not read/write MSR_TSC_AUX from KVM if CPUID bit is not set Paolo Bonzini
2016-03-31 12:56 ` Laszlo Ersek [this message]
2016-03-31 13:12 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2016-03-31 13:23 ` Paolo Bonzini
2016-03-31 15:38 ` Peter Lieven
2016-03-31 16:52 ` Paolo Bonzini
2016-03-31 19:21 ` Peter Lieven
2016-03-31 16:26 ` [Qemu-devel] " Eduardo Habkost
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=56FD1E68.5020604@redhat.com \
--to=lersek@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.