public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Cc: acme@kernel.org, jolsa@redhat.com, namhyung@kernel.org,
	ak@linux.intel.com, Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 0/3] Perf: Some fixes for Alder Lake and Sapphire Rapids
Date: Fri, 18 Jun 2021 08:12:51 -0700	[thread overview]
Message-ID: <1624029174-122219-1-git-send-email-kan.liang@linux.intel.com> (raw)

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

The patchset includes several fixes for a special configuration and
specific events on Alder Lake and Sapphire Rapids.

A single fix patch is easily buried in the numerous LKML emails. So I
put them together to attract more attention.

They are independent small fixes and can be reviewed/merged separately.

Kan Liang (3):
  perf/x86/intel: Fix fixed counter check warning for some Alder Lake
  perf/x86/intel: Add more events requires FRONTEND MSR on Sapphire Rapids
  perf/x86/intel: Fix instructions:ppp support in Sapphire Rapids

 arch/x86/events/intel/core.c | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-06-18 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 15:12 kan.liang [this message]
2021-06-18 15:12 ` [RESEND PATCH 1/3] perf/x86/intel: Fix fixed counter check warning for some Alder Lake kan.liang
2021-06-24  7:09   ` [tip: perf/core] " tip-bot2 for Kan Liang
2021-06-18 15:12 ` [PATCH 2/3] perf/x86/intel: Add more events requires FRONTEND MSR on Sapphire Rapids kan.liang
2021-06-24  7:09   ` [tip: perf/core] " tip-bot2 for Kan Liang
2021-06-18 15:12 ` [PATCH 3/3] perf/x86/intel: Fix instructions:ppp support in " kan.liang
2021-06-24  7:09   ` [tip: perf/core] " tip-bot2 for Kan Liang
2021-06-25  8:27 ` [PATCH 0/3] Perf: Some fixes for Alder Lake and " You-Sheng Yang

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=1624029174-122219-1-git-send-email-kan.liang@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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