On 01.12.2025 17:05, Andrew Cooper wrote: > A XenServer feature in the process of being upstreamed is to be able to > re-caculate the guest CPU Policies at runtime, e.g. after a microcode load > and/or livepatch to expose new functionality. Right now, upstream Xen only > rescans the Raw CPU Policy on microcode load. > > One complication with recalculating the guest policies is that BTC_NO is > handled differently to other $FOO_NO bits, by using __set_bit() rather than > setup_force_cpu_cap(). > > For consistency, switch it to using setup_force_cpu_cap(). This doesn't > matter for upstream Xen right now, but it will ease upstream the feature. > > Signed-off-by: Andrew Cooper <[email protected]>
Acked-by: Jan Beulich <[email protected]>
