Re: [PATCH 4/5] stubdom: Fix -Wimplicit-int in newlib

2025-08-09 Thread Jürgen Groß
On 10.08.25 00:12, Andrew Cooper wrote: This is an error now Debian Trixie's gcc-14 Signed-off-by: Andrew Cooper Reviewed-by: Juergen Gross --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano Stabellini CC: Samuel Thibault CC: Jue

Re: [RFC PATCH 1/3] efi-rtc: Remove wakeup functionality

2025-08-09 Thread Ard Biesheuvel
On Sun, 3 Aug 2025 at 11:05, Alexandre Belloni wrote: > > Hello, > > Apart from the topic that should be "rtc: efi:...", I'm ready to apply > this patch. > Thanks, please go ahead. > On 14/07/2025 08:08:45+0200, Ard Biesheuvel wrote: > > From: Ard Biesheuvel > > > > The EFI rtc driver is used b

[PATCH 2/5] CI: Update ppc64 to use Debian Trixie

2025-08-09 Thread Andrew Cooper
Everything works fine with Debian 13. Provide two new build jobs (for a total of 6), and update the test job. Signed-off-by: Andrew Cooper --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano Stabellini CC: Shawn Anastasio CC: Oleksii Ku

[PATCH 5/5] CI: Update x86 to use Debian Trixie

2025-08-09 Thread Andrew Cooper
With the exception of the custom IBT job, copy all Debian 12 jobs making Debian 13 versions, then trim the Debian 12 ranconfig jobs. Update the test jobs. Signed-off-by: Andrew Cooper --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano St

[PATCH for-4.21 0/5] CI: Add Debian Trixie

2025-08-09 Thread Andrew Cooper
I know it's past the last-post deadline, but Trixie was only released today. In terms of backports, we should at least go back to the bugfix branches. Andrew Cooper (5): CI: Trixie containers CI: Update ppc64 to use Debian Trixie CI: Update riscv64 to use Debian Trixie stubdom: Fix -Wimpl

[PATCH 1/5] CI: Trixie containers

2025-08-09 Thread Andrew Cooper
Debian Trixie has been released. Provide new containers. Signed-off-by: Andrew Cooper --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano Stabellini CC: Shawn Anastasio CC: Oleksii Kurochko CC: Doug Goldstein CC: Marek Marczykowski-Gó

[PATCH 4/5] stubdom: Fix -Wimplicit-int in newlib

2025-08-09 Thread Andrew Cooper
This is an error now Debian Trixie's gcc-14 Signed-off-by: Andrew Cooper --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano Stabellini CC: Samuel Thibault CC: Juergen Gross I really think we need to move onto Unikraft as a maintained

[PATCH 3/5] CI: Update riscv64 to use Debian Trixie

2025-08-09 Thread Andrew Cooper
Everything works fine with Debian 13. Provide two new build jobs, and update both the randconfig the test jobs. Signed-off-by: Andrew Cooper --- CC: Anthony PERARD CC: Michal Orzel CC: Jan Beulich CC: Julien Grall CC: Roger Pau Monné CC: Stefano Stabellini CC: Shawn Anastasio CC: Oleksii

Re: [PATCH v4 2/8] emul/vuart: introduce framework for UART emulators

2025-08-09 Thread dmkhn
On Mon, Aug 04, 2025 at 12:11:03PM +0200, Jan Beulich wrote: > On 31.07.2025 21:21, [email protected] wrote: > > From: Denis Mukhin > > > > Introduce a driver framework to abstract UART emulators in the hypervisor. > > > > That allows for architecture-independent handling of virtual UARTs in the > >

Re: [PATCH v4 5/8] emul/vuart-ns16550: introduce NS16550-compatible UART emulator (x86)

2025-08-09 Thread dmkhn
On Mon, Aug 04, 2025 at 12:53:36PM +0200, Jan Beulich wrote: > On 31.07.2025 21:22, [email protected] wrote: > > From: Denis Mukhin > > > > Add initial in-hypervisor emulator for NS8250/NS16x50-compatible UARTs under > > CONFIG_VUART_NS16550 for x86 port of Xen. > > > > x86 port of Xen lacks vUART f

Re: [PATCH] xen/arm: irq: add missing spin_unlock() in init_local_irq_data() error path

2025-08-09 Thread dmkhn
On Sat, Aug 09, 2025 at 05:32:41PM +0300, Mykola Kvach wrote: > From: Mykola Kvach > > If init_one_irq_desc() fails, init_local_irq_data() returns without > releasing local_irqs_type_lock, leading to a possible deadlock. > > Release the lock before returning to ensure proper cleanup. > > Signed

[PATCH v15 4/4] xen/domain: update create_dom0() messages

2025-08-09 Thread dmkhn
From: Denis Mukhin Use %pd for domain identification in error/panic messages in create_dom0(). No functional change. Signed-off-by: Denis Mukhin Reviewed-by: Alejandro Vallejo Acked-by: Jan Beulich Acked-by: Julien Grall --- Changes since v14: - added Julien's A-b --- xen/arch/arm/domain_

[PATCH v15 2/4] tools/include: move xc_bitops.h to xen-tools/bitops.h

2025-08-09 Thread dmkhn
From: Denis Mukhin Move xc_bitops.h to common tools location to be shared between the toolstack and unit test code. Adjust the guard in xen-tools/bitops.h Correct the #include directives and comments referring to the old xc_bitops.h in the toolstack code. Signed-off-by: Denis Mukhin --- Chan

[PATCH v15 0/4] xen/domain: domain ID allocation

2025-08-09 Thread dmkhn
Patch 1 introduces new domid_{alloc,free} calls. Patch 2 is a prep change for domain ID allocator test. Patch 3 introduces some basic testing for domain ID allocator. Patch 4 adjusts create_dom0() messages (use %pd). Link to v14: https://lore.kernel.org/xen-devel/20250808021938.669855-1-dmuk...@f

[PATCH v15 3/4] tools/tests: introduce unit tests for domain ID allocator

2025-08-09 Thread dmkhn
From: Denis Mukhin Introduce some basic infrastructure for doing domain ID allocation unit tests, and add a few tests that ensure correctness of the domain ID allocator. Use and xen/lib/find-next-bit.c in test hardness code. Adjust find-next-bit.c to be compiled with __XEN_TOOLS__. Signed-of

[PATCH v15 1/4] xen/domain: unify domain ID allocation

2025-08-09 Thread dmkhn
From: Denis Mukhin Currently, there are two different domain ID allocation implementations: 1) Sequential IDs allocation in dom0less Arm code based on max_init_domid; 2) Sequential IDs allocation in XEN_DOMCTL_createdomain; does not use max_init_domid (both Arm and x86). The domain I

Re: [PATCH v14 3/4] tools/tests: introduce unit tests for domain ID allocator

2025-08-09 Thread dmkhn
On Fri, Aug 08, 2025 at 06:56:16PM +0100, Julien Grall wrote: > Hi Denis, > > On 08/08/2025 03:20, [email protected] wrote: > > From: Denis Mukhin > > > > Introduce some basic infrastructure for doing domain ID allocation unit > > tests, > > and add a few tests that ensure correctness of the domai

Re: [PATCH v14 3/4] tools/tests: introduce unit tests for domain ID allocator

2025-08-09 Thread dmkhn
On Fri, Aug 08, 2025 at 06:57:07PM +0100, Julien Grall wrote: > > > On 08/08/2025 18:56, Julien Grall wrote: > > Hi Denis, > > > > On 08/08/2025 03:20, [email protected] wrote: > >> From: Denis Mukhin > >> > >> Introduce some basic infrastructure for doing domain ID allocation > >> unit tests, > >

Re: [PATCH v14 1/4] xen/domain: unify domain ID allocation

2025-08-09 Thread dmkhn
On Fri, Aug 08, 2025 at 06:42:03PM +0100, Julien Grall wrote: > Hi Denis, > > On 08/08/2025 03:19, [email protected] wrote: > > From: Denis Mukhin > > > > Currently, there are two different domain ID allocation implementations: > > > >1) Sequential IDs allocation in dom0less Arm code based on

Re: [PATCH v1 00/16] dma-mapping: migrate to physical address-based API

2025-08-09 Thread Demi Marie Obenour
On 8/9/25 09:34, Jason Gunthorpe wrote: > On Fri, Aug 08, 2025 at 08:51:08PM +0200, Marek Szyprowski wrote: >> First - basing the API on the phys_addr_t. >> >> Page based API had the advantage that it was really hard to abuse it and >> call for something that is not 'a normal RAM'. > > This is n

Re: [XEN PATCH v2 1/3] CI: Rework run-tools-test exit path

2025-08-09 Thread Marek Marczykowski-Górecki
On Wed, Jul 30, 2025 at 05:26:00PM +0200, Anthony PERARD wrote: > From: Anthony PERARD > > The main script expect to find the string "$passed" or it just timeout > and doesn't try to download the junit file in this case. So we ignore > the return value of run-tools-test to always print "$passed"

Re: [XEN PATCH v2 3/3] CI: Workaround extra content in junit

2025-08-09 Thread Marek Marczykowski-Górecki
On Wed, Jul 30, 2025 at 05:26:02PM +0200, Anthony PERARD wrote: > From: Anthony PERARD > > Signed-off-by: Anthony PERARD Is it still an issue? AFAIR similar issue was fixed together with fixing xml upload hanging. > --- > automation/scripts/qubes-x86-64.sh | 6 ++ > 1 file changed, 6 inse

Re: [XEN PATCH v2 2/3] CI: Upload junit result as artefact

2025-08-09 Thread Marek Marczykowski-Górecki
On Wed, Jul 30, 2025 at 05:26:01PM +0200, Anthony PERARD wrote: > From: Anthony PERARD > > This allows to investigate the junit file in cases of parse error. > > Signed-off-by: Anthony PERARD Reviewed-by: Marek Marczykowski-Górecki > --- > > Notes: > Changes in v2: > - more concise p

[PATCH] xen/arm: irq: add missing spin_unlock() in init_local_irq_data() error path

2025-08-09 Thread Mykola Kvach
From: Mykola Kvach If init_one_irq_desc() fails, init_local_irq_data() returns without releasing local_irqs_type_lock, leading to a possible deadlock. Release the lock before returning to ensure proper cleanup. Signed-off-by: Mykola Kvach --- xen/arch/arm/irq.c | 3 +++ 1 file changed, 3 inse

Re: [PATCH v1 00/16] dma-mapping: migrate to physical address-based API

2025-08-09 Thread Jason Gunthorpe
On Fri, Aug 08, 2025 at 08:51:08PM +0200, Marek Szyprowski wrote: > First - basing the API on the phys_addr_t. > > Page based API had the advantage that it was really hard to abuse it and > call for something that is not 'a normal RAM'. This is not true anymore. Today we have ZONE_DEVICE as a s