[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e26b405-f382-45f4-9dd5-3ea5db68302a@intel.com>
Date: Wed, 17 Apr 2024 11:37:37 +0800
From: Xiaoyao Li <xiaoyao.li@...el.com>
To: Reinette Chatre <reinette.chatre@...el.com>, isaku.yamahata@...el.com,
pbonzini@...hat.com, erdemaktas@...gle.com, vkuznets@...hat.com,
seanjc@...gle.com, vannapurve@...gle.com, jmattson@...gle.com,
mlevitsk@...hat.com, chao.gao@...el.com, rick.p.edgecombe@...el.com
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V4 3/4] KVM: x86: Add a capability to configure bus
frequency for APIC timer
On 3/22/2024 12:37 AM, Reinette Chatre wrote:
..
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 0b5a33ee71ee..20080fe4b8ee 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -8063,6 +8063,23 @@ error/annotated fault.
>
> See KVM_EXIT_MEMORY_FAULT for more information.
>
> +7.35 KVM_CAP_X86_APIC_BUS_FREQUENCY
As sean mentioned it previous comment, I would be the one prefers
KVM_CAP_X86_APIC_BUS_CYCLES_NS
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.
Powered by blists - more mailing lists