From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mtosatti@redhat.com, Sergio Lopez <slp@redhat.com>
Subject: Re: [PATCH] x86: Check for machine state object class before typecasting it
Date: Mon, 30 Dec 2019 09:41:14 +0100 [thread overview]
Message-ID: <bda93e70-f737-4384-0422-3901767b6330@redhat.com> (raw)
In-Reply-To: <7cc91bab3191bfd7e071bdd3fdf7fe2a2991deb0.1577692822.git.mprivozn@redhat.com>
On 12/30/19 9:00 AM, Michal Privoznik wrote:
> In v4.2.0-246-ged9e923c3c the SMM property was moved from PC
Typo v4.2.0-246-ged9e923c3c -> ed9e923c3c.
> machine class to x86 machine class. Makes sense, but the change
> was too aggressive: in target/i386/kvm.c:kvm_arch_init() it
> altered check which sets SMRAM if given machine has SMM enabled.
> The line that detects whether given machine object is class of
> PC_MACHINE was removed from the check. This makes qemu try to
> enable SMRAM for all machine types, which is not what we want.
>
Fixes: ed9e923c3c
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
> ---
> target/i386/kvm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 0b511906e3..7ee3202634 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -2173,6 +2173,7 @@ int kvm_arch_init(MachineState *ms, KVMState *s)
> }
>
> if (kvm_check_extension(s, KVM_CAP_X86_SMM) &&
> + object_dynamic_cast(OBJECT(ms), TYPE_X86_MACHINE) &&
> x86_machine_is_smm_enabled(X86_MACHINE(ms))) {
> smram_machine_done.notify = register_smram_listener;
> qemu_add_machine_init_done_notifier(&smram_machine_done);
>
next prev parent reply other threads:[~2019-12-30 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 8:00 [PATCH] x86: Check for machine state object class before typecasting it Michal Privoznik
2019-12-30 8:06 ` no-reply
2019-12-30 8:41 ` Philippe Mathieu-Daudé [this message]
2019-12-30 9:35 ` Michal Prívozník
2019-12-30 9:45 ` Philippe Mathieu-Daudé
2019-12-30 13:17 ` Michal Prívozník
2019-12-30 13:47 ` Philippe Mathieu-Daudé
2020-01-07 10:27 ` 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=bda93e70-f737-4384-0422-3901767b6330@redhat.com \
--to=philmd@redhat.com \
--cc=mprivozn@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
/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).