On 29.05.2025 00:50, dm...@proton.me wrote: > From: Denis Mukhin <dm...@proton.me> > > From: Denis Mukhin <dmuk...@ford.com> > > Embedded deployments of Xen do not need to have support for more than dozen of > domains. > > Introduce build-time configuration option to limit the number of domains > during > run-time. > > Suggested-by: Julien Grall <jul...@xen.org> > Signed-off-by: Denis Mukhin <dmuk...@ford.com> > --- > Changes since v8: > - dropped hunk w/ compile-time check for DOMID_FIRST_RESERVED > - updated CONFIG_MAX_DOMID explanation > - dropped public header file changes > --- > xen/arch/x86/cpu/mcheck/mce.c | 2 +- > xen/arch/x86/cpu/vpmu.c | 2 +- > xen/common/Kconfig | 8 ++++++++ > xen/common/domain.c | 20 +++++++++++--------- > xen/common/sched/core.c | 4 ++-- > xen/drivers/passthrough/vtd/iommu.c | 2 +- > 6 files changed, 24 insertions(+), 14 deletions(-)
What about checks against DOMID_FIRST_RESERVED in common/domctl.c? Indeed they must not be changed, but when not changing them, how are several of the checks you actually change going to be correct? (I'm sorry for noticing this only now; it should have occurred to me earlier on.) Jan
