qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Igor Mammedov <imammedo@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu devel list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] bundling edk2 platform firmware images with QEMU
Date: Fri, 8 Mar 2019 14:09:53 +0100	[thread overview]
Message-ID: <80f0bae3-e79a-bb68-04c4-1c9c684d95b8@redhat.com> (raw)

Hi,

I have a mostly-ready-for-posting patch set for $SUBJECT. My question is
what QEMU release I should be targeting with it.

The Soft Feature Freeze for 4.0 is on 2019-03-12. Here's why that's a
bit inconvenient for me.

The upcoming EDK2 stable release is edk2-stable201903, and it is planned
for... today.

  https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#edk2-stable201903-tag-planning

But, it's being blocked (at least one CVE fix still needs merging, but
there could be something else too). I don't know what that will mean for
the actual tag date. Maybe next Monday (the 11th)?

In my series, I'd like to advance QEMU's roms/edk2 submodule to this new
release. But that might leave us with 1 day before the QEMU 4.0 Soft
Feature Freeze (see above), i.e., for me to post the series, and for a
submaintainer to send a pullreq with it. That's a bit too tight.

I'm not in a mortal rush to get this into 4.0, but the next release
cycles (in three months, approximately?) might align similarly, between
edk2 and QEMU. It would be best to avoid QEMU carrying edk2 platform
firmware that is at all times at least three months old. The main reason
is that CVEs tend to exist, for both edk2 proper, and for the specific
OpenSSL release that is bundled with the given edk2 stable tag. And edk2
doesn't yet have stable *branches*.

Should we try to squeeze my set into 4.0 (possibly moving the Soft
Feature Freeze), or just aim for 4.1?

Also, who'd be the maintainer to queue my set? I mostly thought of Gerd,
due to his work on iPXE and SeaBIOS. Here's the current diffstat:

 Makefile                                       |  17 +-
 pc-bios/README                                 |  11 +
 pc-bios/descriptors/50-edk2-i386-secure.json   |  34 +++
 pc-bios/descriptors/50-edk2-x86_64-secure.json |  35 +++
 pc-bios/descriptors/60-edk2-aarch64.json       |  31 +++
 pc-bios/descriptors/60-edk2-arm.json           |  31 +++
 pc-bios/descriptors/60-edk2-i386.json          |  33 +++
 pc-bios/descriptors/60-edk2-x86_64.json        |  34 +++
 pc-bios/edk2-aarch64-code.fd                   | Bin 0 -> 67108864 bytes
 pc-bios/edk2-arm-code.fd                       | Bin 0 -> 67108864 bytes
 pc-bios/edk2-arm-vars.fd                       | Bin 0 -> 67108864 bytes
 pc-bios/edk2-i386-code.fd                      | Bin 0 -> 3653632 bytes
 pc-bios/edk2-i386-secure-code.fd               | Bin 0 -> 3653632 bytes
 pc-bios/edk2-i386-vars.fd                      | Bin 0 -> 540672 bytes
 pc-bios/edk2-licenses.txt                      | 209 +++++++++++++++
 pc-bios/edk2-x86_64-code.fd                    | Bin 0 -> 3653632 bytes
 pc-bios/edk2-x86_64-secure-code.fd             | Bin 0 -> 3653632 bytes
 roms/Makefile                                  |   9 +-
 roms/Makefile.edk2                             | 134 ++++++++++
 roms/edk2-build.sh                             |  52 ++++
 roms/edk2-funcs.sh                             | 265 ++++++++++++++++++++
 tests/uefi-test-tools/build.sh                 |  97 +------
 22 files changed, 898 insertions(+), 94 deletions(-)

Thanks,
Laszlo

             reply	other threads:[~2019-03-08 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 13:09 Laszlo Ersek [this message]
2019-03-08 13:42 ` [Qemu-devel] bundling edk2 platform firmware images with QEMU Daniel P. Berrangé
2019-03-08 14:20   ` Daniel P. Berrangé
2019-03-08 14:48   ` Laszlo Ersek
2019-03-08 15:06     ` Daniel P. Berrangé
2019-03-08 15:51       ` Igor Mammedov
2019-03-08 16:31         ` Laszlo Ersek
2019-03-08 16:28       ` 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-all 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=80f0bae3-e79a-bb68-04c4-1c9c684d95b8@redhat.com \
    --to=lersek@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).