On 25.07.2025 08:15, Jiqian Chen wrote: > Hi all, > This is a continuation of the disabling some hypercalls handling code series. > https://lore.kernel.org/xen-devel/20250704092952.822578-1-penny.zh...@amd.com/ > > 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. Each hypercall has a separate option to keep > configuration flexible. > > Options to disable hypercalls: > - sysctl > - domctl > - hvm
Is this hvmop? If so, how can it reasonably be disabled when the majority of guests are HVM ones these days? Some of the operations can be invoked by guests on themselves, iirc. > - physdev > - platform_op For everything else, it's not clear whether it was conveyed to you that there is a more general argument against this fine-grained splitting at the Kconfig level. Already with domctl you've learned the hard way that it's intertwined with e.g. sysctl. The basic direction to move into appears to be to allow to exclude such special "management" operations via on single control. In the light of this it's not quite clear how useful it would be to actually review this series. In any event, before anything further can go in, issues with what has already gone in will need sorting, imo. Jan
