From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
David Matlack <dmatlack@google.com>
Subject: Re: [PATCH 0/2] KVM: x86: More cleanups for Hyper-V range flushing
Date: Wed, 05 Apr 2023 16:48:36 +0200 [thread overview]
Message-ID: <87lej6gzaz.fsf@redhat.com> (raw)
In-Reply-To: <20230405003133.419177-1-seanjc@google.com>
Sean Christopherson <seanjc@google.com> writes:
> More cleanups of the code related to Hyper-V's range-based TLB flushing.
> David's series got most of the names, but there are a few more that can
> be converted (patch 1). On top of that, having Hyper-V fill its struct
> provides a decent improvement to code generation, and IMO yields a better
> API (patch 2).
>
> Sean Christopherson (2):
> KVM: x86: Rename Hyper-V remote TLB hooks to match established scheme
> KVM: x86/mmu: Move filling of Hyper-V's TLB range struct into Hyper-V
> code
>
For the series:
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
--
Vitaly
next prev parent reply other threads:[~2023-04-05 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 0:31 [PATCH 0/2] KVM: x86: More cleanups for Hyper-V range flushing Sean Christopherson
2023-04-05 0:31 ` [PATCH 1/2] KVM: x86: Rename Hyper-V remote TLB hooks to match established scheme Sean Christopherson
2023-04-05 0:31 ` [PATCH 2/2] KVM: x86/mmu: Move filling of Hyper-V's TLB range struct into Hyper-V code Sean Christopherson
2023-04-05 14:48 ` Vitaly Kuznetsov [this message]
2023-04-07 20:20 ` [PATCH 0/2] KVM: x86: More cleanups for Hyper-V range flushing David Matlack
2023-04-10 23:30 ` 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=87lej6gzaz.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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