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 C4A2C81E6E for ; Fri, 18 Nov 2016 04:51:54 -0800 (PST) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (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 B5B8A78EA5; Fri, 18 Nov 2016 12:51:58 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-70.phx2.redhat.com [10.3.116.70]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id uAICpvFY018539; Fri, 18 Nov 2016 07:51:57 -0500 To: edk2-devel-01 References: <20161115024308.30612-1-lersek@redhat.com> Cc: Jordan Justen , Paolo Bonzini From: Laszlo Ersek Message-ID: <1465cf46-d924-61d3-e92c-195b199c1661@redhat.com> Date: Fri, 18 Nov 2016 13:51:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161115024308.30612-1-lersek@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Fri, 18 Nov 2016 12:51:58 +0000 (UTC) Subject: Re: [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: Fri, 18 Nov 2016 12:51:54 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 11/15/16 03:43, Laszlo Ersek wrote: > 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(-) > Self-NAK, will send a new version.