From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@ml01.01.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH 1/3] OvmfPkg/SmmControl2Dxe: select broadcast SMI
Date: Tue, 15 Nov 2016 03:43:06 +0100 [thread overview]
Message-ID: <20161115024308.30612-2-lersek@redhat.com> (raw)
In-Reply-To: <20161115024308.30612-1-lersek@redhat.com>
When writing to IO port 0xB2 (ICH9_APM_CNT), QEMU by default injects an
SMI only on the VCPU that is writing the port. This has exposed corner
cases and strange behavior with edk2 code, which generally expects a
software SMI to affect all CPUs at once.
The QEMU patch
hw/isa/lpc_ich9: inject SMI on all VCPUs if APM_STS == 'Q'
adds a side-channel / backdoor to QEMU that enables the firmware to
request a broadcast SMI; namely, by setting IO port 0xB3 (ICH9_APM_STS) to
value 0x51 ('Q') first. (The default behavior cannot be changed because
SeaBIOS depends on it.) Utilize this feature in OVMF's
EFI_SMM_CONTROL2_PROTOCOL.Trigger() method.
The change has no effect on QEMUs that lack the above patch.
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=230
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
OvmfPkg/Include/IndustryStandard/Q35MchIch9.h | 6 ++++--
OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c | 18 +++++++++++++++++-
2 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/OvmfPkg/Include/IndustryStandard/Q35MchIch9.h b/OvmfPkg/Include/IndustryStandard/Q35MchIch9.h
index 4dc2c39901c1..acc05f84b18c 100644
--- a/OvmfPkg/Include/IndustryStandard/Q35MchIch9.h
+++ b/OvmfPkg/Include/IndustryStandard/Q35MchIch9.h
@@ -91,8 +91,10 @@
//
// IO ports
//
-#define ICH9_APM_CNT 0xB2
-#define ICH9_APM_STS 0xB3
+#define ICH9_APM_CNT 0xB2
+
+#define ICH9_APM_STS 0xB3
+#define QEMU_ICH9_APM_STS_BROADCAST_SMI 'Q'
//
// IO ports relative to PMBASE
diff --git a/OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c b/OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c
index 82549b0a7e35..2c987c0cc558 100644
--- a/OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c
+++ b/OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c
@@ -107,10 +107,26 @@ SmmControl2DxeTrigger (
// report about hardware status, while this register is fully governed by
// software.
//
+ // On the QEMU platform, we use the status register to request a "broadcast"
+ // SMI; i.e., to bring all VCPUs into SMM at once. Edk2 handles the case when
+ // the SMI is raised only on the processor that calls Trigger(), but
+ //
+ // - if the processor executing Trigger() is an AP, then the resultant AP-BSP
+ // synchronization is time consuming and computation-hungry,
+ //
+ // - edk2 modules that deal with SMIs generally expect / prefer a software
+ // SMI to affect all CPUs at once; unicast SMIs have exposed obscure corner
+ // cases.
+ //
+ // Note that we exploit the fact that the SMM_CORE never passes a non-NULL
+ // DataPort pointer (that is, we exploit that it doesn't care about the
+ // status register value).
+ //
// Write to the status register first, as this won't trigger the SMI just
// yet. Then write to the control register.
//
- IoWrite8 (ICH9_APM_STS, DataPort == NULL ? 0 : *DataPort);
+ ASSERT (DataPort == NULL);
+ IoWrite8 (ICH9_APM_STS, QEMU_ICH9_APM_STS_BROADCAST_SMI);
IoWrite8 (ICH9_APM_CNT, CommandPort == NULL ? 0 : *CommandPort);
return EFI_SUCCESS;
}
--
2.9.2
next prev parent reply other threads:[~2016-11-15 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 2:43 [PATCH 0/3] OvmfPkg: broadcast SMIs and revert to traditional AP sync mode Laszlo Ersek
2016-11-15 2:43 ` Laszlo Ersek [this message]
2016-11-15 2:43 ` [PATCH 2/3] OvmfPkg: revert "any AP in SMM should not wait for the BSP for more than 100 ms" Laszlo Ersek
2016-11-15 2:43 ` [PATCH 3/3] OvmfPkg: revert "use relaxed AP SMM synchronization mode" Laszlo Ersek
2016-11-18 12:51 ` [PATCH 0/3] OvmfPkg: broadcast SMIs and revert to traditional AP sync mode Laszlo Ersek
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-list 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=20161115024308.30612-2-lersek@redhat.com \
--to=devel@edk2.groups.io \
/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