Re: [PATCH v4 00/24] Disable domctl-op via CONFIG_MGMT_HYPERCALLS

[Jan Beulich <jbeulich@xxxxxxxx>]

On 21.11.2025 11:57, Penny Zheng wrote:
> It can be beneficial for some dom0less systems to further reduce Xen footprint
> via disabling some hypercalls handling code, which may not to be used &
> required in such systems.
> We are introducing a new single Kconfig CONFIG_MGMT_HYPERCALLS to manage
> such hypercalls.
> 
> We are trying to disable hypercalls in the following aspects:
> - sysctl
> - domctl
> - hvm
> - physdev
> - platform
> This patch serie is only focusing on domctl-op. Different aspects will be
> covered in different patch serie.
> 
> Features, like VM event, or paging log-dirty support, which fully rely on
> domctl-op, will be wrapped with CONFIG_MGMT_HYPERCALLS, to reduce Xen
> footprint as much as possible.
> 
> It is derived from Stefano Stabellini's commit "xen: introduce kconfig options
> to disable hypercalls"(
> https://lore.kernel.org/xen-devel/20241219092917.3006174-1-Sergiy_Kibrik@xxxxxxxx)
> ---
> This patch serie is based on two patch serie, one is
> "[XEN][PATCH v4] xen: make VMTRACE support optional" and "
> [PATCH v3 0/7] consolidate vm event subsystem"

While looking at patch 20, I came to wonder what exactly the above means: By the
words, nothing in this series can go in ahead of those other patches. Which 
doesn't
seem quite right. Please can you state dependencies in a helpful (for reviewers 
as
well as committers) way?

Jan