[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <19752b65-5ea2-4ad4-84e4-6b4694bcf976@intel.com>
Date: Thu, 25 Apr 2024 09:39:18 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Sean Christopherson <seanjc@...gle.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
Hi Sean,
On 4/25/2024 9:17 AM, Sean Christopherson wrote:
> 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.
Thank you. I'll resubmit with the capability name changed to
KVM_CAP_X86_APIC_BUS_CYCLES_NS. This is the only planned change.
Reinette
Powered by blists - more mailing lists