From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
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
Subject: Re: [PATCH v2 0/4] KVM: x86: APICv cleanups
Date: Mon, 25 Oct 2021 14:35:50 +0000 [thread overview]
Message-ID: <YXbAxkf1W37m9eZp@google.com> (raw)
In-Reply-To: <b931906f-b38e-1cb5-c797-65ef82c8b262@redhat.com>
On Fri, Oct 22, 2021, Paolo Bonzini wrote:
> So yeah, I think you're right.
Yep. The alternative would be to explicitly check for a pending APICv update.
I don't have a strong opinion, I dislike both options equally :-)
Want me to type up a v3 comment?
next prev parent reply other threads:[~2021-10-25 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 0:49 [PATCH v2 0/4] KVM: x86: APICv cleanups Sean Christopherson
2021-10-22 0:49 ` [PATCH v2 1/4] KVM: x86/mmu: Use vCPU's APICv status when handling APIC_ACCESS memslot Sean Christopherson
2021-10-22 0:49 ` [PATCH v2 2/4] KVM: x86: Move SVM's APICv sanity check to common x86 Sean Christopherson
2021-10-22 0:49 ` [PATCH v2 3/4] KVM: x86: Move apicv_active flag from vCPU to in-kernel local APIC Sean Christopherson
2021-10-22 0:49 ` [PATCH v2 4/4] KVM: x86: Use rw_semaphore for APICv lock to allow vCPU parallelism Sean Christopherson
2021-10-22 10:12 ` [PATCH v2 0/4] KVM: x86: APICv cleanups Paolo Bonzini
2021-10-22 14:56 ` Maxim Levitsky
2021-10-22 16:43 ` Paolo Bonzini
2021-10-25 14:35 ` Sean Christopherson [this message]
2021-10-25 15:21 ` Paolo Bonzini
2021-10-25 15:59 ` Sean Christopherson
2021-10-25 16:05 ` Paolo Bonzini
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=YXbAxkf1W37m9eZp@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.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 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.