From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gleb Natapov <gleb@kernel.org>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH uq/master] kvm: x86: Separately write feature control MSR on reset
Date: Wed, 18 Dec 2013 10:23:42 +0100 [thread overview]
Message-ID: <52B1699E.80006@redhat.com> (raw)
In-Reply-To: <52B0A069.8060807@siemens.com>
Il 17/12/2013 20:05, Jan Kiszka ha scritto:
> If the guest is running in nested mode on system reset, clearing the
> feature MSR signals the kernel to leave this mode. Recent kernels
> processes this properly, but leave the VCPU state undefined behind. It
> is the job of userspace to bring it to a proper shape. Therefore, write
> this specific MSR first so that no state transfer gets lost.
>
> This allows to cleanly reset a guest with VMX in use.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> target-i386/kvm.c | 32 ++++++++++++++++++++++++++++----
> 1 file changed, 28 insertions(+), 4 deletions(-)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 1188482..ec51447 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -1104,6 +1104,25 @@ static int kvm_put_tscdeadline_msr(X86CPU *cpu)
> return kvm_vcpu_ioctl(CPU(cpu), KVM_SET_MSRS, &msr_data);
> }
>
> +/*
> + * Provide a separate write service for the feature control MSR in order to
> + * kick the VCPU out of VMXON or even guest mode on reset. This has to be done
> + * before writing any other state because forcibly leaving nested mode
> + * invalidates the VCPU state.
> + */
> +static int kvm_put_msr_feature_control(X86CPU *cpu)
> +{
> + struct {
> + struct kvm_msrs info;
> + struct kvm_msr_entry entry;
> + } msr_data;
> +
> + kvm_msr_entry_set(&msr_data.entry, MSR_IA32_FEATURE_CONTROL,
> + cpu->env.msr_ia32_feature_control);
> + msr_data.info.nmsrs = 1;
> + return kvm_vcpu_ioctl(CPU(cpu), KVM_SET_MSRS, &msr_data);
> +}
> +
> static int kvm_put_msrs(X86CPU *cpu, int level)
> {
> CPUX86State *env = &cpu->env;
> @@ -1204,10 +1223,8 @@ static int kvm_put_msrs(X86CPU *cpu, int level)
> if (cpu->hyperv_vapic) {
> kvm_msr_entry_set(&msrs[n++], HV_X64_MSR_APIC_ASSIST_PAGE, 0);
> }
> - if (has_msr_feature_control) {
> - kvm_msr_entry_set(&msrs[n++], MSR_IA32_FEATURE_CONTROL,
> - env->msr_ia32_feature_control);
> - }
> + /* Note: MSR_IA32_FEATURE_CONTROL is written separately, see
> + * kvm_put_msr_feature_control. */
> }
> if (env->mcg_cap) {
> int i;
> @@ -1801,6 +1818,13 @@ int kvm_arch_put_registers(CPUState *cpu, int level)
>
> assert(cpu_is_stopped(cpu) || qemu_cpu_is_self(cpu));
>
> + if (level >= KVM_PUT_RESET_STATE && has_msr_feature_control) {
> + ret = kvm_put_msr_feature_control(x86_cpu);
> + if (ret < 0) {
> + return ret;
> + }
> + }
> +
> ret = kvm_getput_regs(x86_cpu, 1);
> if (ret < 0) {
> return ret;
>
Applied, thanks!
prev parent reply other threads:[~2013-12-18 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 19:05 [Qemu-devel] [PATCH uq/master] kvm: x86: Separately write feature control MSR on reset Jan Kiszka
2013-12-18 9:23 ` Paolo Bonzini [this message]
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=52B1699E.80006@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@siemens.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).