mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.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 v6.4
Date: Sun, 25 Jun 2023 11:40:33 +0200	[thread overview]
Message-ID: <20230625094033.GCZJgLkSWnRJfxNXCQ@fat_crate.local> (raw)

Hi Linus,

please pull two urgent perf fixes for 6.4.

Thx.

---

The following changes since commit 858fd168a95c5b9669aac8db6c14a9aeab446375:

  Linux 6.4-rc6 (2023-06-11 14:35:30 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v6.4

for you to fetch changes up to a6742cb90b567f952a95efa27dee345748d09fc7:

  perf/x86/intel: Fix the FRONTEND encoding on GNR and MTL (2023-06-16 16:46:33 +0200)

----------------------------------------------------------------
- Drop the __weak attribute from a function prototype as it otherwise
  leads to the function getting replaced by a dummy stub

- Fix the umask value setup of the frontend event as former is different
  on two Intel cores

----------------------------------------------------------------
Kan Liang (1):
      perf/x86/intel: Fix the FRONTEND encoding on GNR and MTL

Marc Zyngier (1):
      perf/core: Drop __weak attribute from arch_perf_update_userpage() prototype

 arch/x86/events/intel/core.c | 15 ++++++++++++++-
 include/linux/perf_event.h   |  6 +++---
 2 files changed, 17 insertions(+), 4 deletions(-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2023-06-25  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  9:40 Borislav Petkov [this message]
2023-06-25 17:23 ` 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=20230625094033.GCZJgLkSWnRJfxNXCQ@fat_crate.local \
    --to=bp@alien8.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®