Re: 4.18 vs mini-os

[Julien Grall <julien@xxxxxxx>]

+ Juergen

On 16/11/2023 07:52, Jan Beulich wrote:
> All,
Hi Jan,

> may I ask on what basis the xen-RELEASE-4.18.0 tag placement was chosen?
> It matches the 4.17 ones, despite there having been new commits from
> Jürgen dating back to January / February. (My own build fix would have
> been nice to have, too, but I can see how that came late.)
Before the tagging, the last time we updated to MINIOS_UPSTREAM_COMMIT 
was in July 2022 (see below).
When I prepare the release, I don't have steps to check this is the 
latest Mini-OS. Instead, I use the commit in the tag.
I believe this is the responsibility of whoever decide to add a commit 
in Mini-OS to also make sure Config.mk is updated accordingly.
Anyway, we never tested Xen 4.18 (even before RC) with the new Mini-OS. 
So I don't think it is sensible to update it at this stage of the 
release. But I would suggest to send a patch to update Config.mk so the 
problem doesn't re-occur for 4.19.
Cheers,

commit 980bfb1ac9247e95790e283dbc03e231e02cced9
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Fri Jul 8 09:42:27 2022 +0200

    Config.mk: use newest Mini-OS commit

    Switch to use the newest Mini-OS commit in order to get the recent
    fixes.

    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

diff --git a/Config.mk b/Config.mk
index a806ef0afb..e56844d964 100644
--- a/Config.mk
+++ b/Config.mk
@@ -230,7 +230,7 @@ MINIOS_UPSTREAM_URL ?= git://xenbits.xen.org/mini-os.git
 endif
 OVMF_UPSTREAM_REVISION ?= 7b4a99be8a39c12d3a7fc4b8db9f0eab4ac688d5
 QEMU_UPSTREAM_REVISION ?= master
-MINIOS_UPSTREAM_REVISION ?= 83ff43bff4bdd6879539fcb2b3d6ba5e61a64135
+MINIOS_UPSTREAM_REVISION ?= 5bcb28aaeba1c2506a82fab0cdad0201cd9b54b3

 SEABIOS_UPSTREAM_REVISION ?= rel-1.16.0

Cheers,

--
Julien Grall