On 04.12.2024 11:20, Oleksii Kurochko wrote: > This email only tracks big items for xen.git tree. Please reply for items you > would like to see in 4.20 so that people have an idea what is going on and > prioritise accordingly. > > You're welcome to provide description and use cases of the feature you're > working on. > > = Timeline = > > * Last posting date: Nov 29, 2024 > ---> We are here > * Feature freeze date: Dec 20, 2024 > * Hard code freeze: Jan 17, 2025 > * RC1: TBD > * Release: Feb 21, 2025 > ( current release schedule: > https://wiki.xenproject.org/wiki/Xen_Project_X.YY_Release_Notes ) > > All patches that wish to go into 4.20 must be posted no later than the last > posting > date. All patches posted after that date will be automatically queued > into next release. > If you would like your features included in this release, please ensure > they are committed by the deadline. > > RCs will be arranged immediately after freeze. > > The following items ( the links for them could be found int the list below ) > were moved to completed: > - Hypervisor: > * drivers/char: rename arm-uart.c to uart-init.c > * Move gic_preinit() to common code > * stubdom: reduce xenstore library dependencies > * xen/trace: Treewide API cleanup > - x86: > * x86/HVM: drop stdvga caching mode > * Fix module-handling use-after-free's > * Reuse 32 bit C code more safely > * xen: address violations of MISRA C Rule 13.6 > * x86/ucode: Simplify/fix loading paths further > * x86: address violations of MISRA C Rule 16.3 > * iommu/x86: fixes/improvements for unity range checks > * x86/pvh: Support relocating dom0 kernel > - Arm: > * xen/arm: Add emulation of Debug Data Transfer Registers > - RISC-V: > * Setup memory management > > > * Full list of items : *
While only a small single patch, what I think you may want to also keep an eye on is "drop setting XEN_QEMU_CONSOLE_LIMIT in the environment". Jan
