Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 10 Apr 2023 16:30:33 -0700
In-Reply-To: <20230405003133.419177-1-seanjc@google.com>
Mime-Version: 1.0
References: <20230405003133.419177-1-seanjc@google.com>
Message-ID: <168116506851.1036283.16135858065837035509.b4-ty@google.com>
Subject: Re: [PATCH 0/2] KVM: x86: More cleanups for Hyper-V range flushing
From:   Sean Christopherson <seanjc@google.com>
To:     Sean Christopherson <seanjc@google.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Vitaly Kuznetsov <vkuznets@redhat.com>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        David Matlack <dmatlack@google.com>
Content-Type: text/plain; charset="utf-8"
Precedence: bulk

On Tue, 04 Apr 2023 17:31:31 -0700, Sean Christopherson wrote:
> 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
> 
> [...]

Applied to kvm-x86 mmu, thanks!

[1/2] KVM: x86: Rename Hyper-V remote TLB hooks to match established scheme
      https://github.com/kvm-x86/linux/commit/8a1300ff9518
[2/2] KVM: x86/mmu: Move filling of Hyper-V's TLB range struct into Hyper-V code
      https://github.com/kvm-x86/linux/commit/9ed3bf411226

--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes