[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240308013607.GL368614@ls.amr.corp.intel.com>
Date: Thu, 7 Mar 2024 17:36:07 -0800
From: Isaku Yamahata <isaku.yamahata@...ux.intel.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Isaku Yamahata <isaku.yamahata@...el.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
erdemaktas@...gle.com, Vishal Annapurve <vannapurve@...gle.com>,
Jim Mattson <jmattson@...gle.com>,
Maxim Levitsky <mlevitsk@...hat.com>,
Xiaoyao Li <xiaoyao.li@...el.com>, isaku.yamahata@...il.com,
isaku.yamahata@...ux.intel.com
Subject: Re: [PATCH v3 3/4] KVM: X86: Add a capability to configure bus
frequency for APIC timer
On Fri, Feb 23, 2024 at 11:33:54AM -0800,
Sean Christopherson <seanjc@...gle.com> 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@...ux.intel.com>
Powered by blists - more mailing lists