mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jason Baron <jbaron@akamai.com>, seanjc@google.com
Cc: kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Use static_call for kvm_x86_ops
Date: Tue, 26 Jan 2021 17:47:00 +0100	[thread overview]
Message-ID: <7efb7e51-611c-e4eb-be32-fefafb664309@redhat.com> (raw)
In-Reply-To: <cover.1610680941.git.jbaron@akamai.com>

On 15/01/21 04:27, Jason Baron wrote:
> Hi,
> 
> Convert kvm_x86_ops to use static_call. Shows good performance
> gains for cpuid loop micro-benchmark (results in patch 3/3).

Queued, thanks.

Paolo

> Thanks,
> 
> -Jason
> 
> 
> Changes from v1:
> -Introduce kvm-x86-ops header with eye towards using this to define
>   svm_x86_ops and vmx_x86_ops in follow on patches (Paolo, Sean)
> -add new patch (1/3), that adds a vmx/svm prefix to help facilitate
>   svm_x86_ops and vmx_x86_ops future conversions.
> -added amd perf numbres to description of patch 3/3
> 
> Jason Baron (3):
>    KVM: X86: append vmx/svm prefix to additional kvm_x86_ops functions
>    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-x86-ops.h | 127 +++++++++++++++
>   arch/x86/include/asm/kvm_host.h    |  21 ++-
>   arch/x86/kvm/cpuid.c               |   2 +-
>   arch/x86/kvm/hyperv.c              |   4 +-
>   arch/x86/kvm/irq.c                 |   3 +-
>   arch/x86/kvm/kvm_cache_regs.h      |  10 +-
>   arch/x86/kvm/lapic.c               |  30 ++--
>   arch/x86/kvm/mmu.h                 |   6 +-
>   arch/x86/kvm/mmu/mmu.c             |  15 +-
>   arch/x86/kvm/mmu/spte.c            |   2 +-
>   arch/x86/kvm/pmu.c                 |   2 +-
>   arch/x86/kvm/svm/svm.c             |  20 +--
>   arch/x86/kvm/trace.h               |   4 +-
>   arch/x86/kvm/vmx/nested.c          |   2 +-
>   arch/x86/kvm/vmx/vmx.c             |  30 ++--
>   arch/x86/kvm/vmx/vmx.h             |   2 +-
>   arch/x86/kvm/x86.c                 | 307 +++++++++++++++++++------------------
>   arch/x86/kvm/x86.h                 |   6 +-
>   18 files changed, 369 insertions(+), 224 deletions(-)
>   create mode 100644 arch/x86/include/asm/kvm-x86-ops.h
> 


      parent reply	other threads:[~2021-01-27  0:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  3:27 Jason Baron
2021-01-15  3:27 ` [PATCH v2 1/3] KVM: X86: append vmx/svm prefix to additional kvm_x86_ops functions Jason Baron
2021-01-15  9:22   ` Peter Zijlstra
2021-01-15 15:05     ` Jason Baron
2021-01-15  3:27 ` [PATCH v2 2/3] KVM: x86: introduce definitions to support static calls for kvm_x86_ops Jason Baron
2021-01-15  9:26   ` Peter Zijlstra
2021-01-15 13:50     ` Paolo Bonzini
2021-01-15 15:03       ` Jason Baron
2021-01-15  3:27 ` [PATCH v2 3/3] KVM: x86: use static calls to reduce kvm_x86_ops overhead Jason Baron
2021-01-15  9:45   ` Peter Zijlstra
2021-01-15  9:53     ` Peter Zijlstra
2021-01-15  9:54       ` Peter Zijlstra
2021-01-15 13:56     ` Paolo Bonzini
2021-01-26 16:47 ` Paolo Bonzini [this message]

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=7efb7e51-611c-e4eb-be32-fefafb664309@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jbaron@akamai.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®