From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>,
"Guo, Gua" <gua.guo@intel.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Brijesh Singh <brijesh.singh@amd.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Xu, Min M" <min.m.xu@intel.com>,
"Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
Date: Wed, 4 Jan 2023 23:34:50 +0000 [thread overview]
Message-ID: <CO1PR11MB49297A4B1EA2C2CEDCC51FF3D2F59@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230104151234.286030-1-lersek@redhat.com>
Hi Laszlo,
Unit test code coverage was enabled just a couple days ago in CI. Looks like you uncovered a corner case that was missed that should not generate a CI failure.
I have asked Gua to investigate.
Thanks,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Laszlo Ersek
> Sent: Wednesday, January 4, 2023 7:13 AM
> To: devel@edk2.groups.io
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>; Brijesh Singh <brijesh.singh@amd.com>; Aktas, Erdem <erdemaktas@google.com>; Gerd
> Hoffmann <kraxel@redhat.com>; James Bottomley <jejb@linux.ibm.com>; Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Xu, Min M <min.m.xu@intel.com>; Boeuf, Sebastien <sebastien.boeuf@intel.com>; Tom Lendacky
> <thomas.lendacky@amd.com>
> Subject: [edk2-devel] [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
>
> Repo: https://pagure.io/lersek/edk2.git
> Branch: cpuhp-reg-catch-4250
> Test build: https://github.com/tianocore/edk2/pull/3853
> Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=4250
>
> NOTE: the test build linked above (in the github.com CI env) *failed*.
> That's because the CI environment is affected by this very QEMU bug!
>
> Namely, the following checks failed -- due to the intentional hang
> introduced in this patch:
>
> - PlatformCI_OvmfPkg_Ubuntu_GCC5_PR (12 tests)
> - PlatformCI_OvmfPkg_Windows_VS2019_PR (11 tests)
>
> (The Build_VS2019_TARGET_CODE_COVERAGE and
> Build_GCC5_TARGET_CODE_COVERAGE tests also failed, but those seem bogus
> to me.)
>
> All 12+11=23 PlatformCI_OvmfPkg_* checks failed due to timeout, and the
> firmware logs of the DEBUG and NOOPT builds end with:
>
> > INFO - PlatformMaxCpuCountInitialization: Broken CPU hotplug register block: Present=0 Possible=1.
> > INFO - PlatformMaxCpuCountInitialization: Switch QEMU's acceleration from TCG to KVM, or update QEMU.
> > INFO - PlatformMaxCpuCountInitialization: Refer to <https://bugzilla.tianocore.org/show_bug.cgi?id=4250>.
> > INFO - ASSERT /home/vsts/work/1/s/OvmfPkg/Library/PlatformInitLib/Platform.c(574): ((BOOLEAN)(0==1))
>
> So I'm not proposing to merge this immediately; something must be fixed
> first:
>
> - use KVM in the CI env, or
>
> - delay this patch until my QEMU fix is merged, and a new release is
> made, and the new QEMU release is packaged by the distros, and the new
> distro packages are picked up by github.com CI.
>
> Suggestions?
>
> Thanks,
> Laszlo
>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Brijesh Singh <brijesh.singh@amd.com>
> Cc: Erdem Aktas <erdemaktas@google.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: James Bottomley <jejb@linux.ibm.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Min Xu <min.m.xu@intel.com>
> Cc: Sebastien Boeuf <sebastien.boeuf@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
>
> Laszlo Ersek (1):
> OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
>
> OvmfPkg/Library/PlatformInitLib/Platform.c | 34 ++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
>
>
>
>
next prev parent reply other threads:[~2023-01-04 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 15:12 [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression Laszlo Ersek
2023-01-04 15:12 ` [PATCH 1/1] " Laszlo Ersek
2023-01-05 13:12 ` Gerd Hoffmann
2023-01-04 23:34 ` Michael D Kinney [this message]
2023-01-05 5:39 ` [edk2-devel] [PATCH 0/1] " Guo, Gua
2023-01-05 15:15 ` Laszlo Ersek
2023-01-05 15:17 ` Laszlo Ersek
2023-01-05 13:12 ` Gerd Hoffmann
2023-01-05 13:43 ` Oliver Steffen
2023-01-05 13:52 ` Gerd Hoffmann
2023-01-05 15:12 ` Laszlo Ersek
2023-01-05 15:18 ` Oliver Steffen
[not found] ` <173772B56BF8C7B8.2132@groups.io>
2023-01-09 9:49 ` [edk2-devel] " Oliver Steffen
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=CO1PR11MB49297A4B1EA2C2CEDCC51FF3D2F59@CO1PR11MB4929.namprd11.prod.outlook.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