xen/arm: Clarify how the domid is decided in create_domUs()
authorLuca Fancellu <luca.fancellu@arm.com>
Wed, 14 Apr 2021 09:14:03 +0000 (10:14 +0100)
committerJulien Grall <jgrall@amazon.com>
Thu, 15 Apr 2021 17:08:29 +0000 (18:08 +0100)
commitb3d1f523c8de3a6657b11456a56bd8f5e67e247b
tree2d87b4859603f6d343e722bf9f743e049722cfc9
parent784d70d68342d20074d88ee8d8bab41b9210505f
xen/arm: Clarify how the domid is decided in create_domUs()

This patch adds a comment in create_domUs() right before
domain_create() to explain the importance of the pre-increment
operator on the variable max_init_domid, to ensure that the
domid 0 is allocated only during start_xen() function by the
create_dom0() and not on any other possible code path to the
domain_create() function.

Signed-off-by: Luca Fancellu <luca.fancellu@arm.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>
Acked-by: Julien Grall <jgrall@amazon.com>
xen/arch/arm/domain_build.c