On Fri, Feb 23, 2024 at 11:33:54AM -0800, Sean Christopherson <seanjc@xxxxxxxxxx> wrote: > On Tue, Dec 19, 2023, Isaku Yamahata wrote: > > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst > > index 7025b3751027..cc976df2651e 100644 > > --- a/Documentation/virt/kvm/api.rst > > +++ b/Documentation/virt/kvm/api.rst > > @@ -7858,6 +7858,20 @@ This capability is aimed to mitigate the threat that malicious VMs can > > cause CPU stuck (due to event windows don't open up) and make the CPU > > unavailable to host or other VMs. > > > > +7.34 KVM_CAP_X86_BUS_FREQUENCY_CONTROL > > BUS_FREQUENCY_CONTROL is simultaneously too long, yet not descriptive enough. > Depending on whether people get hung up on nanoseconds not being a "frequency", > either KVM_CAP_X86_APIC_BUS_FREQUENCY or KVM_CAP_X86_APIC_BUS_CYCLES_NS. > > Also, this series needs to be rebased onto kvm-x86/next. Thanks for the feedback with the concrete change to the patch. I agree with those for the next respin. -- Isaku Yamahata <isaku.yamahata@xxxxxxxxxxxxxxx>
