[Public] Hi,
> -----Original Message----- > From: Jan Beulich <[email protected]> > Sent: Tuesday, June 10, 2025 9:41 PM > To: Penny, Zheng <[email protected]> > Cc: Huang, Ray <[email protected]>; Andrew Cooper > <[email protected]>; Roger Pau Monné <[email protected]>; > Anthony PERARD <[email protected]>; Orzel, Michal > <[email protected]>; Julien Grall <[email protected]>; Stefano Stabellini > <[email protected]>; [email protected] > Subject: Re: [PATCH v4 11/20] xen/pmstat: introduce CONFIG_PM_OP > > On 28.05.2025 11:16, Penny Zheng wrote: > > --- a/xen/common/Kconfig > > +++ b/xen/common/Kconfig > > @@ -591,4 +591,11 @@ config SYSCTL > > to reduce Xen footprint. > > endmenu > > > > +config PM_OP > > + bool "Enable Performance Management Operation" > > + depends on ACPI && HAS_CPUFREQ && SYSCTL > > + default y > > + help > > + This option shall enable userspace performance management control > > + to do power/performance analyzing and tuning. > > endmenu > > Why is this being added outside of the "Supported hypercall interfaces" > menu? (No matter where it's added, please make sure there's a separating blank > line ahdead of the subsequent "endmenu".) Because, I intended to have the only five catogory under "Supported hypercall interfaces": - sysctl - domctl - hvm - physdev - platform Which will be introduced in a patch serie and may contain multiple different features. PM_OP is more or less a feature to me. And it is only dependent on SYSCTL, like LIVEPATCH, etc > > Jan
