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/[email protected]/.

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

Reply via email to