From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] i386: do not migrate MSR_SMI_COUNT on machine types <2.12
Date: Tue, 24 Jul 2018 15:44:13 +0100 [thread overview]
Message-ID: <20180724144412.GC2374@work-vm> (raw)
In-Reply-To: <20180724120003.27053-1-pbonzini@redhat.com>
* Paolo Bonzini (pbonzini@redhat.com) wrote:
> MSR_SMI_COUNT started being migrated in QEMU 2.12. Do not migrate it
> on older machine types, or the subsection causes a load failure for
> guests that use SMM.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> include/hw/i386/pc.h | 4 ++++
> target/i386/cpu.c | 2 ++
> target/i386/cpu.h | 1 +
> target/i386/machine.c | 2 +-
> 4 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
> index 654003f44c..6894f37df1 100644
> --- a/include/hw/i386/pc.h
> +++ b/include/hw/i386/pc.h
> @@ -317,6 +317,10 @@ bool e820_get_entry(int, uint32_t, uint64_t *, uint64_t *);
> #define PC_COMPAT_2_11 \
> HW_COMPAT_2_11 \
> {\
> + .driver = TYPE_X86_CPU,\
> + .property = "x-migrate-smi-count",\
> + .value = "off",\
> + },{\
> .driver = "Skylake-Server" "-" TYPE_X86_CPU,\
> .property = "clflushopt",\
> .value = "off",\
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index e0e2f2eea1..92732ef1a0 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -5435,6 +5435,8 @@ static Property x86_cpu_properties[] = {
> false),
> DEFINE_PROP_BOOL("vmware-cpuid-freq", X86CPU, vmware_cpuid_freq, true),
> DEFINE_PROP_BOOL("tcg-cpuid", X86CPU, expose_tcg, true),
> + DEFINE_PROP_BOOL("x-migrate-smi-count", X86CPU, migrate_smi_count,
> + false),
Shouldn't that be true?
(and then turned off in the compat)
Dave
> /*
> * lecacy_cache defaults to true unless the CPU model provides its
> * own cache information (see x86_cpu_load_def()).
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index 2c5a0d90a6..bcda6197a8 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -1379,6 +1379,7 @@ struct X86CPU {
> bool expose_kvm;
> bool expose_tcg;
> bool migratable;
> + bool migrate_smi_count;
> bool max_features; /* Enable all supported features automatically */
> uint32_t apic_id;
>
> diff --git a/target/i386/machine.c b/target/i386/machine.c
> index 8b64dff487..084c2c73a8 100644
> --- a/target/i386/machine.c
> +++ b/target/i386/machine.c
> @@ -400,7 +400,7 @@ static bool msr_smi_count_needed(void *opaque)
> X86CPU *cpu = opaque;
> CPUX86State *env = &cpu->env;
>
> - return env->msr_smi_count != 0;
> + return cpu->migrate_smi_count && env->msr_smi_count != 0;
> }
>
> static const VMStateDescription vmstate_msr_smi_count = {
> --
> 2.17.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-07-24 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 12:00 [Qemu-devel] [PATCH] i386: do not migrate MSR_SMI_COUNT on machine types <2.12 Paolo Bonzini
2018-07-24 14:44 ` Dr. David Alan Gilbert [this message]
2018-07-24 14:45 ` 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=20180724144412.GC2374@work-vm \
--to=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--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).