On 8/29/25 19:21, dmuk...@xen.org wrote:
> 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 v16:
> https://lore.kernel.org/xen-devel/20250812223024.2364749-1-dmuk...@ford.com/
> Link to CI:
> https://gitlab.com/xen-project/people/dmukhin/xen/-/pipelines/2012378054
>
> Denis Mukhin (4):
> xen/domain: unify domain ID allocation
> tools/include: move xc_bitops.h to xen-tools/bitops.h
> tools/tests: introduce unit tests for domain ID allocator
> xen/domain: update create_dom0() messages
>
> .../xen-tools/bitops.h} | 16 +++-
> tools/libs/ctrl/xc_misc.c | 13 +--
> tools/libs/guest/xg_dom_elfloader.c | 1 -
> tools/libs/guest/xg_dom_hvmloader.c | 1 -
> tools/libs/guest/xg_private.h | 2 +-
> tools/libs/guest/xg_sr_common.h | 2 -
> tools/tests/Makefile | 1 +
> tools/tests/domid/.gitignore | 2 +
> tools/tests/domid/Makefile | 88 +++++++++++++++++
> tools/tests/domid/harness.h | 54 +++++++++++
> tools/tests/domid/test-domid.c | 95 +++++++++++++++++++
> xen/arch/arm/domain_build.c | 13 ++-
> xen/arch/x86/setup.c | 11 ++-
> xen/common/Makefile | 1 +
> xen/common/device-tree/dom0less-build.c | 15 +--
> xen/common/domain.c | 2 +
> xen/common/domctl.c | 43 ++-------
> xen/common/domid.c | 95 +++++++++++++++++++
> xen/include/xen/domain.h | 3 +
> xen/lib/find-next-bit.c | 5 +
> 20 files changed, 397 insertions(+), 66 deletions(-)
> rename tools/{libs/ctrl/xc_bitops.h => include/xen-tools/bitops.h} (84%)
> create mode 100644 tools/tests/domid/.gitignore
> create mode 100644 tools/tests/domid/Makefile
> create mode 100644 tools/tests/domid/harness.h
> create mode 100644 tools/tests/domid/test-domid.c
> create mode 100644 xen/common/domid.cWould it make sense to support virtualizing the domain ID space? That would allow the toolstack to only allow a domain to communicate with other domains of its choosing, rather than with any domain XSM permits. This would also allow avoiding domain ID reuse problems, because a virtual domain ID would stay valid even after the domain it refers to no longer exists. It would need to be explicitly released by the guest kernel before it could refer to a different domain. -- Sincerely, Demi Marie Obenour (she/her/hers)
OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
