All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] perf event updates for v6.4
Date: Thu, 27 Apr 2023 22:38:04 +0200	[thread overview]
Message-ID: <ZErdLD+FWUjx08ey@gmail.com> (raw)


Linus,

Please pull the latest perf/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-2023-04-27

   # HEAD: 743767d6f6b8f28228be181fe369657f7ecd1eb2 perf/x86/intel/uncore: Add events for Intel SPR IMC PMU

Perf changes for v6.4:

 - Add Intel Granite Rapids support

 - Add uncore events for Intel SPR IMC PMU

 - Fix perf IRQ throttling bug

 Thanks,

	Ingo

------------------>
Artem Bityutskiy (1):
      perf/x86/cstate: Add Granite Rapids support

Kan Liang (2):
      perf/x86/intel: Add Granite Rapids
      perf/x86/msr: Add Granite Rapids

Stephane Eranian (1):
      perf/x86/intel/uncore: Add events for Intel SPR IMC PMU

Yang Jihong (1):
      perf/core: Fix hardlockup failure caused by perf throttle


 arch/x86/events/intel/core.c         | 16 ++++++++++++++--
 arch/x86/events/intel/cstate.c       |  2 ++
 arch/x86/events/intel/uncore_snbep.c | 12 ++++++++++++
 arch/x86/events/msr.c                |  2 ++
 kernel/events/core.c                 |  4 ++--
 5 files changed, 32 insertions(+), 4 deletions(-)

             reply	other threads:[~2023-04-27 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 20:38 Ingo Molnar [this message]
2023-04-28 22:04 ` [GIT PULL] perf event updates for v6.4 pr-tracker-bot

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=ZErdLD+FWUjx08ey@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.