From: Reinette Chatre <reinette.chatre@intel.com>
To: Sean Christopherson <seanjc@google.com>,
<isaku.yamahata@intel.com>, <pbonzini@redhat.com>,
<erdemaktas@google.com>, <vkuznets@redhat.com>,
<vannapurve@google.com>, <jmattson@google.com>,
<mlevitsk@redhat.com>, <xiaoyao.li@intel.com>,
<chao.gao@intel.com>, <rick.p.edgecombe@intel.com>,
<yuan.yao@intel.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V9 0/2] KVM: x86: Make bus clock frequency for vAPIC timer configurable
Date: Fri, 28 Jun 2024 17:10:45 -0700 [thread overview]
Message-ID: <5354a7ae-ca32-42fe-9231-a0d955bc8675@intel.com> (raw)
In-Reply-To: <171961507216.241377.3829798983563243860.b4-ty@google.com>
Hi Sean,
On 6/28/24 3:55 PM, Sean Christopherson wrote:
> On Wed, 12 Jun 2024 11:16:10 -0700, Reinette Chatre wrote:
>> Changes from v8:
>> - v8: https://lore.kernel.org/lkml/cover.1718043121.git.reinette.chatre@intel.com/
>> - Many changes to new udelay() utility patch as well as the APIC bus
>> frequency test aimed to make it more robust (additional ASSERTs,
>> consistent types, eliminate duplicate code, etc.) and useful with
>> support for more user configuration. Please refer to individual patches for
>> detailed changes.
>> - Series applies cleanly to next branch of kvm-x86 with HEAD
>> e4e9e1067138e5620cf0500c3e5f6ebfb9d322c8.
>>
>> [...]
>
> Applied to kvm-x86 misc, with all the changes mentioned in my earlier replies.
> I'm out next week, and don't want to merge the KVM changes without these tests,
> hence the rushed application.
>
> Please holler if you disagree with anything (or if I broke something). I won't
> respond until July 8th at the earliest, but worst case scenario we can do fixup
> patches after 6.11-rc1.
Thank you very much for taking the time to make the changes and apply the patches.
All the changes look good to me and passes my testing.
Now that the x86 udelay() utility no longer use cpu_relax(), should ARM
and RISC-V's udelay() be modified to match in this regard? I can prepare
(unable to test) changes for you to consider on your return.
Reinette
next prev parent reply other threads:[~2024-06-29 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 18:16 [PATCH V9 0/2] KVM: x86: Make bus clock frequency for vAPIC timer configurable Reinette Chatre
2024-06-12 18:16 ` [PATCH V9 1/2] KVM: selftests: Add x86_64 guest udelay() utility Reinette Chatre
2024-06-28 22:46 ` Sean Christopherson
2024-06-12 18:16 ` [PATCH V9 2/2] KVM: selftests: Add test for configure of x86 APIC bus frequency Reinette Chatre
2024-06-28 22:50 ` Sean Christopherson
2024-06-29 0:39 ` VMX Preemption Timer appears to be buggy on SKX, CLX, and ICX Sean Christopherson
2024-07-03 20:14 ` Reinette Chatre
2024-07-03 21:37 ` Reinette Chatre
2024-07-08 5:55 ` Yuan Yao
2026-05-13 1:31 ` Chao Gao
2026-05-14 21:09 ` Sean Christopherson
2026-05-15 6:34 ` Chao Gao
2024-06-28 22:55 ` [PATCH V9 0/2] KVM: x86: Make bus clock frequency for vAPIC timer configurable Sean Christopherson
2024-06-29 0:10 ` Reinette Chatre [this message]
2024-07-10 15:42 ` Sean Christopherson
2024-07-10 17:14 ` 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=5354a7ae-ca32-42fe-9231-a0d955bc8675@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 \
--cc=yuan.yao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.