public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Steffen" <osteffen@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: 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>,
	 Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH 0/1] OvmfPkg/PlatformInitLib: catch QEMU's CPU hotplug reg block regression
Date: Mon, 9 Jan 2023 10:49:37 +0100	[thread overview]
Message-ID: <CA+bRGFrxN=63XTiLu87geUUpOpxfKzdQWtaUBna6Zu9_ihmYig@mail.gmail.com> (raw)
In-Reply-To: <173772B56BF8C7B8.2132@groups.io>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Thu, Jan 5, 2023 at 4:19 PM Oliver Steffen <osteffen@redhat.com> wrote:

> Quoting Laszlo Ersek (2023-01-05 16:12:36)
> > On 1/5/23 14:52, Gerd Hoffmann wrote:
> > > On Thu, Jan 05, 2023 at 02:43:32PM +0100, Oliver Steffen wrote:
> > >> Quoting Gerd Hoffmann (2023-01-05 14:12:22)
> > >>> Not sure this is an option.  Is nested virtualization supported in
> azure
> > >>> pipeline VMs?  If so, is /dev/kvm passed into containers?
> > >>
> > >> I doubt it, but need to check.
> > >
> > >>> That requires updating the fedora containers though.  I think they
> are
> > >>> at Fedora 35 still, which is EOL meanwhile, so no more updates ...
> > >>
> > >> Yes, it is Fedora 35, because we were (are?) not ready for gcc 12 yet.
> > >
> > > The gcc12 fix finally landed
> (129404f6e4395008ac0045e7e627edbba2a1e064),
> > > so yes, we are ready now.
> > >
> > >> Currently we are building Qemu is from scratch anyway (instead of
> > >> using the Fedora 35 repo) becasue we needed a recent one, see
> > >>
> https://github.com/tianocore/containers/blob/main/Fedora-35/Dockerfile#L75
> > >
> > > Alternative to self-compiling is using
> > > https://fedoraproject.org/wiki/Virtualization_Preview_Repository
> > > for a more recent qemu version.
> >
> > Ah, those options all sound great. I didn't expect it was possible to
> > use self-built (or otherwise "externally sourced") QEMUs in CI!
>
> I would prefer the tar download since it is a rather long lived and
> version-stable source. We a trying to pin down the version numbers the
> most relevant tools so that they don't "run away"/update without
> intent.
>
> I'll also check if we can run the CI with gcc 12.
>
Unfortunately, the EDK2 CI as a whole is not ready for gcc 12. RiscV64
builds fail:

  RiscV64/FlushCache.iiii:16: Error: unrecognized opcode `fence.i'

Here we are hitting a downside of the approach of relying on
distro-packages.

-Oliver

[-- Attachment #2: Type: text/html, Size: 3294 bytes --]

      parent reply	other threads:[~2023-01-09  9:49 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 ` [edk2-devel] [PATCH 0/1] " Michael D Kinney
2023-01-05  5:39   ` 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           ` Oliver Steffen [this message]

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='CA+bRGFrxN=63XTiLu87geUUpOpxfKzdQWtaUBna6Zu9_ihmYig@mail.gmail.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