From: Reinette Chatre <reinette.chatre@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Rick P Edgecombe <rick.p.edgecombe@intel.com>,
"jmattson@google.com" <jmattson@google.com>,
Chao Gao <chao.gao@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
Vishal Annapurve <vannapurve@google.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Erdem Aktas <erdemaktas@google.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable
Date: Thu, 25 Apr 2024 09:39:18 -0700 [thread overview]
Message-ID: <19752b65-5ea2-4ad4-84e4-6b4694bcf976@intel.com> (raw)
In-Reply-To: <ZiqCCo9WipMgWy8K@google.com>
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
next prev parent reply other threads:[~2024-04-25 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:37 [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable Reinette Chatre
2024-03-21 16:37 ` [PATCH V4 1/4] KVM: x86: hyper-v: Calculate APIC bus frequency for Hyper-V Reinette Chatre
2024-04-16 17:07 ` Edgecombe, Rick P
2024-03-21 16:37 ` [PATCH V4 2/4] KVM: x86: Make nsec per APIC bus cycle a VM variable Reinette Chatre
2024-04-16 17:08 ` Edgecombe, Rick P
2024-03-21 16:37 ` [PATCH V4 3/4] KVM: x86: Add a capability to configure bus frequency for APIC timer Reinette Chatre
2024-04-16 17:08 ` Edgecombe, Rick P
2024-04-16 21:28 ` Reinette Chatre
2024-04-17 3:37 ` Xiaoyao Li
2024-03-21 16:37 ` [PATCH V4 4/4] KVM: selftests: Add test for configure of x86 APIC bus frequency Reinette Chatre
2024-04-16 17:09 ` [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable Edgecombe, Rick P
2024-04-24 16:13 ` Sean Christopherson
2024-04-24 16:38 ` Edgecombe, Rick P
2024-04-24 17:23 ` Sean Christopherson
2024-04-24 18:10 ` Edgecombe, Rick P
2024-04-24 19:57 ` Sean Christopherson
2024-04-24 21:20 ` Reinette Chatre
2024-04-25 16:17 ` Sean Christopherson
2024-04-25 16:39 ` Reinette Chatre [this message]
2024-04-24 21:07 ` Reinette Chatre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19752b65-5ea2-4ad4-84e4-6b4694bcf976@intel.com \
--to=reinette.chatre@intel.com \
--cc=chao.gao@intel.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=vkuznets@redhat.com \
--cc=xiaoyao.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).