From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PULL 01/10] hw/acpi/ich9: clear smi_en on reset
Date: Mon, 27 Jul 2015 23:50:08 +0300 [thread overview]
Message-ID: <20150727234906-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <be66680e8320d612f1c96096a217e642e458f47b.1438026619.git.mjt@msgid.tls.msk.ru>
On Mon, Jul 27, 2015 at 10:54:04PM +0300, Michael Tokarev wrote:
> From: Laszlo Ersek <lersek@redhat.com>
>
> Otherwise on reboot firmware might think (due to APMC_EN remaining set
> from the previous boot) that SMI support is absent.
>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: qemu-trivial@nongnu.org
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Confused. Why are you merging these patches through your tree?
I was preparing a pull request myself, while likely git
will figure it out fine, this commit will appear twice in
history and it's kind of messy.
I guess I could drop this - but it's more work ...
> ---
> hw/acpi/ich9.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/acpi/ich9.c b/hw/acpi/ich9.c
> index f04f6dc..8da5a2d 100644
> --- a/hw/acpi/ich9.c
> +++ b/hw/acpi/ich9.c
> @@ -221,6 +221,7 @@ static void pm_reset(void *opaque)
> acpi_pm_tmr_reset(&pm->acpi_regs);
> acpi_gpe_reset(&pm->acpi_regs);
>
> + pm->smi_en = 0;
> if (!pm->smm_enabled) {
> /* Mark SMM as already inited to prevent SMM from running. KVM does not
> * support SMM mode. */
> --
> 2.1.4
next prev parent reply other threads:[~2015-07-27 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 19:54 [Qemu-devel] [PULL for-2.4 00/10] Trivial patches for 2015-07-27 Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 01/10] hw/acpi/ich9: clear smi_en on reset Michael Tokarev
2015-07-27 20:50 ` Michael S. Tsirkin [this message]
2015-07-27 20:54 ` Michael S. Tsirkin
2015-07-27 19:54 ` [Qemu-devel] [PULL 02/10] hw/acpi/ich9: clean up stale comment about KVM not supporting SMM Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 03/10] device_tree: Fix a typo Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 04/10] qemu-common.h: Document cutils.c string functions Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 05/10] make: Clean build messages Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 06/10] vmstate: remove unused declaration Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 07/10] gitignore: Ignore shader generated files Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 08/10] Fix Cortex-A9 global timer Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 09/10] qapi: add missing @ Michael Tokarev
2015-07-27 19:54 ` [Qemu-devel] [PULL 10/10] gdbstub: Set current CPU on interruptions Michael Tokarev
2015-07-28 12:22 ` [Qemu-devel] [PULL for-2.4 00/10] Trivial patches for 2015-07-27 Peter Maydell
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=20150727234906-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).