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.16-rc1
Date: Sun, 14 Nov 2021 11:41:10 +0100 [thread overview]
Message-ID: <YZDnxpLswv1HwBaz@zn.tnic> (raw)
Hi Linus,
please pull a couple of perf/urgent fixes before v5.16-rc1 releases.
Thx.
---
The following changes since commit debe436e77c72fcee804fb867f275e6d31aa999c:
Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2021-11-10 17:05:37 -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.16_rc1
for you to fetch changes up to 4716023a8f6a0f4a28047f14dd7ebdc319606b84:
perf/core: Avoid put_page() when GUP fails (2021-11-11 13:09:34 +0100)
----------------------------------------------------------------
- Prevent unintentional page sharing by checking whether a page
reference to a PMU samples page has been acquired properly before that
- Make sure the LBR_SELECT MSR is saved/restored too
- Reset the LBR_SELECT MSR when resetting the LBR PMU to clear any
residual data left
----------------------------------------------------------------
Greg Thelen (1):
perf/core: Avoid put_page() when GUP fails
Like Xu (1):
perf/x86/vlbr: Add c->flags to vlbr event constraints
Wanpeng Li (1):
perf/x86/lbr: Reset LBR_SELECT during vlbr reset
arch/x86/events/intel/core.c | 4 +++-
arch/x86/events/intel/lbr.c | 2 ++
kernel/events/core.c | 10 +++++-----
3 files changed, 10 insertions(+), 6 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next reply other threads:[~2021-11-14 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 10:41 Borislav Petkov [this message]
2021-11-14 17:52 ` pr-tracker-bot
2021-11-21 15:09 [GIT pull] " Thomas Gleixner
2021-11-21 19:39 ` 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=YZDnxpLswv1HwBaz@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®