From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86/mmu: Declare flush_remote_tlbs{_range}() hooks iff HYPERV!=n
Date: Thu, 19 Oct 2023 08:57:08 -0700 [thread overview]
Message-ID: <ZTFR1HLRoNdYxVa4@google.com> (raw)
In-Reply-To: <87wmvj57hk.fsf@redhat.com>
On Thu, Oct 19, 2023, Vitaly Kuznetsov wrote:
> I can take it to my CONFIG_KVM_HYPERV series but it doesn't seem to
> intersect with it so I guess there's no need for that.
Yeah, I checked before sending (I've had this patch lying around for quite some
time). I was quite surprised that there wasn't any overlap.
next prev parent reply other threads:[~2023-10-19 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 19:23 [PATCH] KVM: x86/mmu: Declare flush_remote_tlbs{_range}() hooks iff HYPERV!=n Sean Christopherson
2023-10-19 8:41 ` Vitaly Kuznetsov
2023-10-19 15:57 ` Sean Christopherson [this message]
2023-11-30 1:44 ` Sean Christopherson
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=ZTFR1HLRoNdYxVa4@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.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