From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by mx.groups.io with SMTP id smtpd.web10.79917.1673589844193762386
 for <devel@edk2.groups.io>;
 Thu, 12 Jan 2023 22:04:04 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jVv+0j0h;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1673589843;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=IXMN/h4IGFDmZS9RfQcyKo8sBMKxS5pqCElSWmzFJts=;
	b=jVv+0j0hL+cDnYwXld8tyebEaWfp1LU2tufdf/ol8pAdlkK+loF4SXJtw1akktV0jshWmS
	Kk85wzGOmSxhvtNWIVOVf1tczCc5AvBl5U2JZUnWTRbd6sr+DwLYTUmA30ZEE6Wrtl344R
	t+3yxFobX9ceINbFBmr6DRepYul50qA=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com
 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-540-J4oS6gG9NC2XbZZl04-6Ew-1; Fri, 13 Jan 2023 01:03:57 -0500
X-MC-Unique: J4oS6gG9NC2XbZZl04-6Ew-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 8A8093804063;
	Fri, 13 Jan 2023 06:03:56 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.238])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 298D51759E;
	Fri, 13 Jan 2023 06:03:56 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 904CA180060F; Fri, 13 Jan 2023 07:03:54 +0100 (CET)
Date: Fri, 13 Jan 2023 07:03:54 +0100
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Brown <mcb30@ipxe.org>, devel@edk2.groups.io,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Erdem Aktas <erdemaktas@google.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Min Xu <min.m.xu@intel.com>, Oliver Steffen <osteffen@redhat.com>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH v2] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
Message-ID: <20230113060354.siony3rjwpgzd5tk@sirius.home.kraxel.org>
References: <20230112082845.128463-1-lersek@redhat.com>
 <01020185a568604c-e16d8581-963a-4ff3-8566-bf0640ad327d-000000@eu-west-1.amazonses.com>
 <407c5cee-7a6c-cbc8-35cc-8f2c2724914c@redhat.com>
 <01020185a6bda78a-05d82180-4d1a-4af4-9a9b-ac78088d11ed-000000@eu-west-1.amazonses.com>
 <49e4e8bb-3bbd-0ca8-ee59-e75560deffa7@redhat.com>
MIME-Version: 1.0
In-Reply-To: <49e4e8bb-3bbd-0ca8-ee59-e75560deffa7@redhat.com>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

  Hi,

> - QEMU can be configured with other compat properties on the command
> line so that "CPU hotplug with SMI" and "CPU hot-unplug with SMI" *not*
> be offered to the firmware. Then QEMU will reject hotplug attempts, and
> the SMM hotplug code in edk2 will not be triggered by the (virtual)
> hardware.

Can we have edk2 print instructions for that in the error message?
We also might switch edk2 CI to run qemu that way.

take care,
  Gerd