From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9857981E57 for ; Mon, 14 Nov 2016 18:43:09 -0800 (PST) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D39B47F7DB; Tue, 15 Nov 2016 02:43:13 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-50.phx2.redhat.com [10.3.116.50]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id uAF2hCZu032444; Mon, 14 Nov 2016 21:43:12 -0500 From: Laszlo Ersek To: edk2-devel-01 Cc: Jordan Justen , Paolo Bonzini Date: Tue, 15 Nov 2016 03:43:05 +0100 Message-Id: <20161115024308.30612-1-lersek@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Tue, 15 Nov 2016 02:43:14 +0000 (UTC) Subject: [PATCH 0/3] OvmfPkg: broadcast SMIs and revert to traditional AP sync mode X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 02:43:09 -0000 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 ) 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 Cc: Paolo Bonzini 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