Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 0/2] Use static_call for kvm_x86_ops
To:     Jason Baron <jbaron@akamai.com>, kvm@vger.kernel.org
Cc:     tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
        peterz@infradead.org, aarcange@redhat.com, x86@kernel.org,
        linux-kernel@vger.kernel.org
References: <cover.1610379877.git.jbaron@akamai.com>
From:   Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <f56312ed-32d5-f1ca-8ca8-6de20daa955e@redhat.com>
Date:   Mon, 11 Jan 2021 18:31:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <cover.1610379877.git.jbaron@akamai.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 11/01/21 17:57, Jason Baron wrote:
> Hi,
> 
> Convert kvm_x86_ops to use static_call. Shows good performance
> gains for cpuid loop micro-benchmark (resulsts included in patch 2).
> 
> Thanks,
> 
> -Jason
> 
> Jason Baron (2):
>    KVM: x86: introduce definitions to support static calls for kvm_x86_ops
>    KVM: x86: use static calls to reduce kvm_x86_ops overhead
> 
>   arch/x86/include/asm/kvm_host.h |  71 +++++++++-
>   arch/x86/kvm/cpuid.c            |   2 +-
>   arch/x86/kvm/hyperv.c           |   4 +-
>   arch/x86/kvm/irq.c              |   2 +-
>   arch/x86/kvm/kvm_cache_regs.h   |  10 +-
>   arch/x86/kvm/lapic.c            |  28 ++--
>   arch/x86/kvm/mmu.h              |   6 +-
>   arch/x86/kvm/mmu/mmu.c          |  12 +-
>   arch/x86/kvm/mmu/spte.c         |   2 +-
>   arch/x86/kvm/pmu.c              |   2 +-
>   arch/x86/kvm/trace.h            |   4 +-
>   arch/x86/kvm/x86.c              | 299 ++++++++++++++++++++--------------------
>   arch/x86/kvm/x86.h              |   6 +-
>   13 files changed, 259 insertions(+), 189 deletions(-)
> 

Thank you thank you thank you! :)

(Except that now I have to find another task for a new KVM developer, 
but that's not a big deal).

Paolo