On Sun, May 18, 2025 at 10:52:24AM +0200, Jan Beulich wrote:
> On 16.05.2025 04:04, dm...@proton.me wrote:
> > From: Denis Mukhin
> >
> > Currently, hypervisor code has two different non-system domain ID allocation
> > implementations:
> >
> > (a) Sequential IDs allocation in dom0less Arm code b
On 16.05.2025 04:04, dm...@proton.me wrote:
> From: Denis Mukhin
>
> Currently, hypervisor code has two different non-system domain ID allocation
> implementations:
>
> (a) Sequential IDs allocation in dom0less Arm code based on max_init_domid;
>
> (b) Sequential IDs allocation in XEN_DOMCT
On Fri, May 16, 2025 at 09:35:35PM +0100, Julien Grall wrote:
> Hi Denis and Teddy,
>
> I haven't looked at the rest of the series. Just answering
> to the discussion between both of you.
>
> On 16/05/2025 19:06, dm...@proton.me wrote:
> > On Fri, May 16, 2025 at 08:43:35AM +, Teddy Astie wro
Hi Denis and Teddy,
I haven't looked at the rest of the series. Just answering
to the discussion between both of you.
On 16/05/2025 19:06, dm...@proton.me wrote:
On Fri, May 16, 2025 at 08:43:35AM +, Teddy Astie wrote:
diff --git a/xen/common/device-tree/dom0less-build.c
b/xen/common/devi
On Fri, May 16, 2025 at 08:43:35AM +, Teddy Astie wrote:
> Hello,
>
> Le 16/05/2025 à 04:06, dm...@proton.me a écrit :
> > From: Denis Mukhin
> >
> > Currently, hypervisor code has two different non-system domain ID allocation
> > implementations:
> >
> >(a) Sequential IDs allocation in d
Hello,
Le 16/05/2025 à 04:06, dm...@proton.me a écrit :
> From: Denis Mukhin
>
> Currently, hypervisor code has two different non-system domain ID allocation
> implementations:
>
>(a) Sequential IDs allocation in dom0less Arm code based on max_init_domid;
>
>(b) Sequential IDs allocation
From: Denis Mukhin
Currently, hypervisor code has two different non-system domain ID allocation
implementations:
(a) Sequential IDs allocation in dom0less Arm code based on max_init_domid;
(b) Sequential IDs allocation in XEN_DOMCTL_createdomain; does not use
max_init_domid (both Arm
