From: Andrew Cooper <firstname.lastname@example.org>
To: Ian Jackson <email@example.com>, <firstname.lastname@example.org>,
Cc: "Jan Beulich" <email@example.com>,
"Frédéric Pierret" <firstname.lastname@example.org>,
"Dario Faggioli" <email@example.com>
Subject: Re: [ANNOUNCE] Xen 4.15 release update - still in feature freeze
Date: Mon, 15 Mar 2021 13:10:11 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 15/03/2021 12:18, Ian Jackson wrote:
> OPEN ISSUES AND BLOCKERS
> io-apic issue on Ryzen 1800X
> Related Qubes issue tracking this:
> Information from
> Jan Beulich <email@example.com>
> Andrew Cooper <firstname.lastname@example.org>
> Frédéric Pierret <email@example.com>
> ABI stability checking
> [PATCH for-4.15 00/10] tools: Support to use abi-dumper on libraries
> [PATCH v2 for-4.15] tools/libxl: Work around unintialised variable libxl__domain_get_device_model_uid()
The libxl thing is already committed (2ff2adc61fcfa0).
> This is testing/build work and will enable ABI checking of future
> changes to 4.15 after its release. I don't think it's a blocker but
> it would be nice to have.
> My most recent impression is that there are still some loose ends
Plan 1 (committing dumps into the tree) won't work. Plan 2 (OSSTest and
other systems doing a double checkout) probably does require a tweak or
two in 4.15 to make it easy to start in 4.16.
Also, "xenstore_lib.h and libxenstore API/ABI problems" still has work
to do for 4.15.
> ISSUES BELIEVED NEWLY RESOLVED
> Fallout from MSR handling behavioral change.
> I think there are now no outstanding patches to fix/change MSR
> behaviour and there is no longer any blocker here ?
Still one known issue remaining, as pointed out in Roger's summary. I'm
still working on it.
next prev parent reply other threads:[~2021-03-15 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 12:18 [ANNOUNCE] Xen 4.15 release update - still in feature freeze Ian Jackson
2021-03-15 13:10 ` Andrew Cooper [this message]
2021-03-15 13:46 ` Jan Beulich
2021-03-16 9:43 ` Roger Pau Monné
2021-03-16 10:12 ` Jan Beulich
2021-03-18 18:11 ` Dario Faggioli
2021-03-29 17:16 ` Dario Faggioli
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.