Re: [PATCH v11 1/3] xen/domain: unify domain ID allocation

[dmkhn@proton.me]

On Tue, Jul 29, 2025 at 12:34:25PM +0200, Alejandro Vallejo wrote:

Thanks for review!

> On Mon Jul 28, 2025 at 8:34 PM CEST, dmkhn wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > 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 ID allocation covers dom0 or late hwdom, predefined domains,
> > post-boot domains, excluding Xen system domains (domid >=
> > DOMID_FIRST_RESERVED).
> >
> > It makes sense to have a common helper code for such task across architectures
> > (Arm and x86) and between dom0less / toolstack domU allocation.
> >
> > Note, fixing dependency on max_init_domid is out of scope of this patch.
> 
> I can see why. The console switch code is a bit annoying. It's unfortunate it
> relies on that global for the early wraparound.

Yep, I have a series which removes `max_init_domid` here:
  https://lore.kernel.org/xen-devel/20250530231841.73386-1-dmukhin@ford.com/