From: Jan Beulich <jbeulich@suse.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: committers@xenproject.org,
Community Manager <community.manager@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] CHANGELOG.md: Update for 4.21 release cycle
Date: Fri, 26 Sep 2025 07:49:27 +0200 [thread overview]
Message-ID: <68350569-4e53-4845-b3df-22ec15e4ee30@suse.com> (raw)
In-Reply-To: <97488f35-3f94-42b0-8443-4feacf3d587d@gmail.com>
On 25.09.2025 22:22, Oleksii Kurochko wrote:
> On 9/25/25 8:26 AM, Jan Beulich wrote:
>> On 24.09.2025 11:36, Oleksii Kurochko wrote:
>>> --- a/CHANGELOG.md
>>> +++ b/CHANGELOG.md
>>> @@ -14,6 +14,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>> - Debian Trixie added to CI. Debian Bullseye retired from CI for RISC-V due
>>> to the baseline change.
>>> - Linux based device model stubdomains are now fully supported.
>>> + - Remove libxenctrl usage from xenstored.
>>>
>>> - On x86:
>>> - Restrict the cache flushing done as a result of guest physical memory map
>>> @@ -21,6 +22,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>> - Allow controlling the MTRR cache attribute of the Xen platform PCI device
>>> BAR for HVM guests, to improve performance of guests using it to map the
>>> grant table or foreign memory.
>>> + - Allow to unflatten DTs.
>> What is this about? There continues to be no use of DT on x86, so without context
>> this feels pretty much meaningless to me.
>
> I am referring tohttps://lore.kernel.org/xen-devel/20250722000525.7247-1-alejandro.garciavallejo@amd.com/.
Sure, but what practical use does this have for anyone using Xen?
>>> @@ -36,11 +38,20 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>> - Support in hvmloader for new SMBIOS tables: 7 (Cache Info), 8 (Port
>>> Connector), 9 (System Slots), 26 (Voltage Probe), 27 (Cooling Device),
>>> and 28 (Temperature Probe).
>>> + - Basic kexec support to Mini-OS for running in PVH mode.
>> Hmm, MiniOS isn't an integral part of a Xen release, so I wonder if such really
>> belongs here. Yes, I also understand that there's not really anywhere else to
>> put such.
>
> I decided to put it here since we include information about stubdoms in|CHANGELOG.md|,
> and MiniOS is related to that.
Stubdom code is part of the git repo and hence the tarball. MiniOS isn't.
Jan
next prev parent reply other threads:[~2025-09-26 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 9:36 [PATCH] CHANGELOG.md: Update for 4.21 release cycle Oleksii Kurochko
2025-09-25 6:26 ` Jan Beulich
2025-09-25 20:22 ` Oleksii Kurochko
2025-09-26 5:49 ` Jan Beulich [this message]
2025-09-26 6:43 ` Juergen Gross
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=68350569-4e53-4845-b3df-22ec15e4ee30@suse.com \
--to=jbeulich@suse.com \
--cc=committers@xenproject.org \
--cc=community.manager@xenproject.org \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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 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.