public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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 0/3] OvmfPkg: broadcast SMIs and revert to traditional AP sync mode
Date: Tue, 15 Nov 2016 03:43:05 +0100	[thread overview]
Message-ID: <20161115024308.30612-1-lersek@redhat.com> (raw)

Spurred by Jiewen's and Jeff's recent SMM-related work, Paolo and I
stress-tested OVMF's SMM a little bit, and with S3 it turns out to be
less stable than ideal.

Paolo agreed / suggested that we add a broadcast SMI mode to QEMU, and
utilize it from OVMF:

  https://www.mail-archive.com/edk2-devel@lists.01.org/msg19669.html

I sent the QEMU patch a few minutes (or hours?) ago:

  http://lists.nongnu.org/archive/html/qemu-devel/2016-11/msg02687.html

and these are the OVMF patches that put the QEMU functionality to use.

With these patches (and with Jeff's just-committed series for
<https://bugzilla.tianocore.org/show_bug.cgi?id=216>) I see stable and
reliable behavior with SMM+S3. Please see

  https://lists.01.org/pipermail/edk2-devel/2016-November/004682.html

for details.

Repo:   https://github.com/lersek/edk2/
Branch: broadcast_smi
BZ:     https://bugzilla.tianocore.org/show_bug.cgi?id=230

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>

Thanks
Laszlo

Laszlo Ersek (3):
  OvmfPkg/SmmControl2Dxe: select broadcast SMI
  OvmfPkg: revert "any AP in SMM should not wait for the BSP for more
    than 100 ms"
  OvmfPkg: revert "use relaxed AP SMM synchronization mode"

 OvmfPkg/OvmfPkgIa32.dsc                       |  2 --
 OvmfPkg/OvmfPkgIa32X64.dsc                    |  2 --
 OvmfPkg/OvmfPkgX64.dsc                        |  2 --
 OvmfPkg/Include/IndustryStandard/Q35MchIch9.h |  6 ++++--
 OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c       | 18 +++++++++++++++++-
 5 files changed, 21 insertions(+), 9 deletions(-)

-- 
2.9.2



             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 Laszlo Ersek [this message]
2016-11-15  2:43 ` [PATCH 1/3] OvmfPkg/SmmControl2Dxe: select broadcast SMI Laszlo Ersek
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-1-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