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.12-rc3
Date: Sun, 14 Mar 2021 13:44:11 +0100 [thread overview]
Message-ID: <20210314124411.GC27191@zn.tnic> (raw)
Hi Linus,
please pull there perf urgent fixes for v5.12-rc3.
Thx.
---
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/perf_urgent_for_v5.12-rc3
for you to fetch changes up to c8e2fe13d1d1f3a02842b7b909d4e4846a4b6a2c:
x86/perf: Use RET0 as default for guest_get_msrs to handle "no PMU" case (2021-03-10 16:45:09 +0100)
----------------------------------------------------------------
- Make sure PMU internal buffers are flushed for per-CPU events too and
properly handle PID/TID for large PEBS.
- Handle the case properly when there's no PMU and therefore return an
empty list of perf MSRs for VMX to switch instead of reading random
garbage from the stack.
----------------------------------------------------------------
Kan Liang (2):
perf/core: Flush PMU internal buffers for per-CPU events
perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR
Sean Christopherson (1):
x86/perf: Use RET0 as default for guest_get_msrs to handle "no PMU" case
arch/x86/events/core.c | 15 ++++++---------
arch/x86/events/intel/core.c | 5 ++++-
arch/x86/kvm/vmx/vmx.c | 2 +-
include/linux/perf_event.h | 2 ++
kernel/events/core.c | 42 ++++++++++++++++++++++++++++++++++++++----
5 files changed, 51 insertions(+), 15 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2021-03-14 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 12:44 Borislav Petkov [this message]
2021-03-14 20:01 ` [GIT PULL] perf/urgent for v5.12-rc3 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=20210314124411.GC27191@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