mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] perf/urgent for v5.18-rc2
Date: Sun, 10 Apr 2022 13:29:55 +0200	[thread overview]
Message-ID: <YlK/syONzEUgRsgV@zn.tnic> (raw)

Hi Linus,

somewhat more urgent perf fixes for 5.18-rc2 but that's normal, I guess,
considering we're still early in the cycle.

Please pull,
thx.

---

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v5.18_rc2

for you to fetch changes up to e19cd0b6fa5938c51d7b928010d584f0de93913a:

  perf/core: Always set cpuctx cgrp when enable cgroup event (2022-04-05 09:59:45 +0200)

----------------------------------------------------------------
- A couple of fixes to cgroup-related handling of perf events

- A couple of fixes to event encoding on Sapphire Rapids

- Pass event caps of inherited events so that perf doesn't fail wrongly at fork()

- Add support for a new Raptor Lake CPU

----------------------------------------------------------------
Chengming Zhou (4):
      perf/core: Don't pass task around when ctx sched in
      perf/core: Use perf_cgroup_info->active to check if cgroup is active
      perf/core: Fix perf_cgroup_switch()
      perf/core: Always set cpuctx cgrp when enable cgroup event

Kan Liang (6):
      perf/x86: Add Intel Raptor Lake support
      perf/x86/cstate: Add Raptor Lake support
      perf/x86/msr: Add Raptor Lake CPU support
      perf/x86/uncore: Add Raptor Lake uncore support
      perf/x86/intel: Don't extend the pseudo-encoding to GP counters
      perf/x86/intel: Update the FRONTEND MSR mask on Sapphire Rapids

Namhyung Kim (1):
      perf/core: Inherit event_caps

 arch/x86/events/intel/core.c       |   9 +-
 arch/x86/events/intel/cstate.c     |  22 ++--
 arch/x86/events/intel/uncore.c     |   1 +
 arch/x86/events/intel/uncore_snb.c |  20 ++++
 arch/x86/events/msr.c              |   1 +
 arch/x86/include/asm/perf_event.h  |   5 +
 kernel/events/core.c               | 212 ++++++++++---------------------------
 7 files changed, 101 insertions(+), 169 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg

             reply	other threads:[~2022-04-10 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 11:29 Borislav Petkov [this message]
2022-04-10 17:52 ` 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=YlK/syONzEUgRsgV@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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®