mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Like Xu <like.xu.linux@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Like Xu <likexu@tencent.com>
Subject: [PATCH 0/7] KVM: x86/pmu: Four functional fixes
Date: Fri, 12 Nov 2021 17:51:32 +0800	[thread overview]
Message-ID: <20211112095139.21775-1-likexu@tencent.com> (raw)

Hi,

The first one (patch 01) is to fix my childish code about the disallowed
fixed ctr3. 

The second one (patch 02) is to fix the aged inconsistent behaviour
about CPUID 0AH.EBX. 

The third one (patch 03/04) is to avoid perf_event creation for
unavailable Intel CPUID events.

Finally a new way is proposed to
fix amd_event_mapping[] for new AMD platforms.

Please check each commit message for more details
and let me know if there is any room for improvement,

Thanks.

Like Xu (7):
  KVM: x86/pmu: Make top-down.slots event unavailable in supported leaf
  KVM: x86/pmu: Fix available_event_types check for REF_CPU_CYCLES event
  KVM: x86/pmu: Pass "struct kvm_pmu *" to the find_fixed_event()
  KVM: x86/pmu: Avoid perf_event creation for invalid counter config
  KVM: x86/pmu: Refactor pmu->available_event_types field using BITMAP
  perf: x86/core: Add interface to query perfmon_event_map[] directly
  KVM: x86/pmu: Setup the {inte|amd}_event_mapping[] when hardware_setup

 arch/x86/events/core.c            |   9 +++
 arch/x86/include/asm/kvm_host.h   |   2 +-
 arch/x86/include/asm/perf_event.h |   5 ++
 arch/x86/kvm/cpuid.c              |  14 ++++
 arch/x86/kvm/pmu.c                |  35 +++++++++-
 arch/x86/kvm/pmu.h                |   4 +-
 arch/x86/kvm/svm/pmu.c            |  24 ++-----
 arch/x86/kvm/vmx/pmu_intel.c      | 106 +++++++++++++++++++++++-------
 arch/x86/kvm/x86.c                |   1 +
 9 files changed, 153 insertions(+), 47 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-11-12  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  9:51 Like Xu [this message]
2021-11-12  9:51 ` [PATCH 1/7] KVM: x86/pmu: Make top-down.slots event unavailable in supported leaf Like Xu
2021-11-12  9:51 ` [PATCH 2/7] KVM: x86/pmu: Fix available_event_types check for REF_CPU_CYCLES event Like Xu
2021-11-12  9:51 ` [PATCH 3/7] KVM: x86/pmu: Pass "struct kvm_pmu *" to the find_fixed_event() Like Xu
2021-11-12  9:51 ` [PATCH 4/7] KVM: x86/pmu: Avoid perf_event creation for invalid counter config Like Xu
2021-11-12  9:51 ` [PATCH 5/7] KVM: x86/pmu: Refactor pmu->available_event_types field using BITMAP Like Xu
2021-11-12  9:51 ` [PATCH 6/7] perf: x86/core: Add interface to query perfmon_event_map[] directly Like Xu
2021-11-17 23:21   ` kernel test robot
2021-11-18  8:06     ` Like Xu
2021-11-18 13:36       ` Like Xu
2021-11-12  9:51 ` [PATCH 7/7] KVM: x86/pmu: Setup the {inte|amd}_event_mapping[] when hardware_setup Like Xu
2021-11-25 13:18   ` [KVM] 54244a5dd7: BUG:KASAN:stack-out-of-bounds_in_find_first_bit kernel test robot

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=20211112095139.21775-1-likexu@tencent.com \
    --to=like.xu.linux@gmail.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.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

all inboxes | Powered by JetHome®