From: Haozhong Zhang <haozhong.zhang@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>, Marcelo Tosatti <mtosatti@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [PATCH] target-i386: check vcpu features before accessing MSR_TSC_AUX
Date: Mon, 14 Dec 2015 21:54:31 +0800 [thread overview]
Message-ID: <20151214135430.GA1526@hz-desktop.sh.intel.com> (raw)
In-Reply-To: <566EAD47.8020004@redhat.com>
On 12/14/15 12:51, Paolo Bonzini wrote:
>
>
> On 14/12/2015 12:07, Haozhong Zhang wrote:
> > This patch fix a bug that prevents VM rebooting on recent versions of
> > KVM (from commit 9dbe6cf).
> >
> > kvm_get_msrs() is called to save guest MSR_TSC_AUX and other MSRs across
> > rebooting. It only checks whether KVM exposes MSR_TSC_AUX to userspace.
> > However, if vcpu does not support rdtscp (e.g. kvm64), current KVM will
> > fail the saving and thus all other MSRs following it will fail in
> > kvm_get_msrs(). As a result, from KVM commit 9dbe6cf that exposes
> > MSR_TSC_AUX, VM can not successfully reboot.
> >
> > This patch fixes this bug by adding the missing rdtscp feature checks.
>
> That commit is not in any released kernel.
Right, it's currently only in kvm next. But I assume it would finally come
into a released kernel.
> It's better if we just check
> msr_info->host_initiated in vmx_get_msr and vmx_set_msr. Can you prepare
> a patch?
>
Yes, I'll send a KVM patch later. And then this QEMU patch is not
needed any more.
Haozhong
next prev parent reply other threads:[~2015-12-14 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 11:07 [PATCH] target-i386: check vcpu features before accessing MSR_TSC_AUX Haozhong Zhang
2015-12-14 11:51 ` Paolo Bonzini
2015-12-14 13:54 ` Haozhong Zhang [this message]
2015-12-14 13:55 ` Paolo Bonzini
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=20151214135430.GA1526@hz-desktop.sh.intel.com \
--to=haozhong.zhang@intel.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rth@twiddle.net \
/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