public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	"Jordan Justen" <jordan.l.justen@intel.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 0/2] OvmfPkg: fix race conditions in VCPU hotplug (for edk2-stable202008)
Date: Thu, 27 Aug 2020 09:50:27 +0200	[thread overview]
Message-ID: <165fce27-1f9b-f28b-34d6-4edd4fa93c9a@arm.com> (raw)
In-Reply-To: <20200826222129.25798-1-lersek@redhat.com>

On 8/27/20 12:21 AM, Laszlo Ersek wrote:
> Ref:    https://bugzilla.tianocore.org/show_bug.cgi?id=2929
> Repo:   https://pagure.io/lersek/edk2.git
> Branch: cpu_hotplug_races_bz_2929
> 
> Proposing these bugfixes for edk2-stable202008. We should either include
> them in the release, or revert commit 5ba203b54e59
> ("OvmfPkg/SmmControl2Dxe: negotiate ICH9_LPC_SMI_F_CPU_HOTPLUG",
> 2020-08-24). Please see the BZ for more details.
> 
> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
> 


For the series,

Reviewed-by: Ard Biesheuvel <ard.biesheuvel@arm.com>

I have no objections to incorporating these changes into the upcoming 
stable tag.


  parent reply	other threads:[~2020-08-27  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 22:21 [PATCH 0/2] OvmfPkg: fix race conditions in VCPU hotplug (for edk2-stable202008) Laszlo Ersek
2020-08-26 22:21 ` [PATCH 1/2] OvmfPkg/CpuHotplugSmm: fix CPU hotplug race just before SMI broadcast Laszlo Ersek
2020-08-26 22:21 ` [PATCH 2/2] OvmfPkg/CpuHotplugSmm: fix CPU hotplug race just after " Laszlo Ersek
2020-08-27  7:50 ` Ard Biesheuvel [this message]
2020-08-27 18:14   ` [edk2-devel] [PATCH 0/2] OvmfPkg: fix race conditions in VCPU hotplug (for edk2-stable202008) 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=165fce27-1f9b-f28b-34d6-4edd4fa93c9a@arm.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