[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZiqCCo9WipMgWy8K@google.com>
Date: Thu, 25 Apr 2024 09:17:14 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Reinette Chatre <reinette.chatre@...el.com>
Cc: Rick P Edgecombe <rick.p.edgecombe@...el.com>, "jmattson@...gle.com" <jmattson@...gle.com>,
Chao Gao <chao.gao@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "vkuznets@...hat.com" <vkuznets@...hat.com>,
Vishal Annapurve <vannapurve@...gle.com>, Xiaoyao Li <xiaoyao.li@...el.com>,
Erdem Aktas <erdemaktas@...gle.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>,
"mlevitsk@...hat.com" <mlevitsk@...hat.com>, Isaku Yamahata <isaku.yamahata@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable
On Wed, Apr 24, 2024, Reinette Chatre wrote:
> There was one vote for the capability name to rather be KVM_CAP_X86_APIC_BUS_CYCLES_NS [1]
>
> I'd be happy to resubmit with the name changed but after reading your
> statement above it is not clear to me what name is preferred:
> KVM_CAP_X86_APIC_BUS_FREQUENCY as used in this series that seem to meet your
> approval or KVM_CAP_X86_APIC_BUS_CYCLES_NS.
>
> Please let me know what you prefer.
Both work for me, I don't have a strong preference.
Powered by blists - more mailing lists