mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@kernel.org, acme@kernel.org,
	namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org
Cc: ak@linux.intel.com, eranian@google.com,
	Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 0/3] perf/x86/intel: Various small fixes for core PMU
Date: Mon,  8 Jul 2024 12:33:33 -0700	[thread overview]
Message-ID: <20240708193336.1192217-1-kan.liang@linux.intel.com> (raw)

From: Kan Liang <kan.liang@linux.intel.com>

Several small fixes for core PMU were sent in the past few months. They
were buried in the LKML. The patch set is to resend them.

These patches are standalone and can be merged separately.

Patch 1 is to hide unenumerated Topdowm metrics events.
The original patch can be found at
https://lore.kernel.org/lkml/20231219150109.1596634-1-kan.liang@linux.intel.com/

Patch 2 is to add a distinct name for Granite Rapids
The original patch can be found at
https://lore.kernel.org/lkml/20240426150557.2857936-1-kan.liang@linux.intel.com/

Patch 3 is to fix non 0 retire latency on Raptor Lake
The original patch can be found at
https://lore.kernel.org/lkml/20240405143032.1243201-1-kan.liang@linux.intel.com/

Kan Liang (3):
  perf/x86/intel: Hide Topdown metrics events if the feature is not
    enumerated
  perf/x86/intel: Add a distinct name for Granite Rapids
  perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake

 arch/x86/events/intel/core.c | 43 ++++++++++++++++++++++++++++++++----
 arch/x86/events/intel/ds.c   |  8 +++++--
 2 files changed, 45 insertions(+), 6 deletions(-)

-- 
2.38.1


             reply	other threads:[~2024-07-08 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 19:33 kan.liang [this message]
2024-07-08 19:33 ` [PATCH 1/3] perf/x86/intel: Hide Topdown metrics events if the feature is not enumerated kan.liang
2024-07-09 11:41   ` [tip: perf/core] " tip-bot2 for Kan Liang
2024-07-08 19:33 ` [PATCH 2/3] perf/x86/intel: Add a distinct name for Granite Rapids kan.liang
2024-07-09  9:56   ` Peter Zijlstra
2024-07-09 12:56     ` Liang, Kan
2024-07-09 11:41   ` [tip: perf/core] " tip-bot2 for Kan Liang
2024-07-08 19:33 ` [PATCH 3/3] perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake kan.liang
2024-07-09 11:41   ` [tip: perf/core] " tip-bot2 for Kan Liang

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=20240708193336.1192217-1-kan.liang@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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®