From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
luferry <luferry@163.com>
Subject: Re: [PATCH 0/2] KVM: VMX: Avoid RDMSRs in PI x2APIC checks
Date: Mon, 18 Jan 2021 19:24:23 +0100 [thread overview]
Message-ID: <d9d59280-0f68-6af0-82d0-87d1eda69a07@redhat.com> (raw)
In-Reply-To: <20210115220354.434807-1-seanjc@google.com>
On 15/01/21 23:03, Sean Christopherson wrote:
> Resurrect a patch[*] from over a year ago to avoid RDMSR in a fairly hot
> path in KVM's posted interrupt support. Note, in my response to that
> patch, I suggested checking x2apic_supported() as well as x2apic_mode. I
> have no idea why I suggested that; unless I'm missing something,
> x2apic_mode can never be set if x2apic_supported() is false.
>
> [*] https://lkml.kernel.org/r/20190723130608.26528-1-luferry@163.com/
>
> Sean Christopherson (2):
> x86/apic: Export x2apic_mode for use by KVM in "warm" path
> KVM: VMX: Use x2apic_mode to avoid RDMSR when querying PI state
>
> arch/x86/kernel/apic/apic.c | 1 +
> arch/x86/kvm/vmx/posted_intr.c | 6 +++---
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-01-18 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 22:03 [PATCH 0/2] KVM: VMX: Avoid RDMSRs in PI x2APIC checks Sean Christopherson
2021-01-15 22:03 ` [PATCH 1/2] x86/apic: Export x2apic_mode for use by KVM in "warm" path Sean Christopherson
2021-01-15 22:03 ` [PATCH 2/2] KVM: VMX: Use x2apic_mode to avoid RDMSR when querying PI state Sean Christopherson
2021-01-18 18:24 ` Paolo Bonzini [this message]
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=d9d59280-0f68-6af0-82d0-87d1eda69a07@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luferry@163.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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 NNTP newsgroup(s).