public inbox for linux-kernel@vger.kernel.org
 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.15-rc4
Date: Sun, 3 Oct 2021 11:55:33 +0200	[thread overview]
Message-ID: <YVl+FSNMK3BSy9gd@zn.tnic> (raw)

Hi Linus,

please pull three urgent perf fixes for v5.15.

Thx.

---

The following changes since commit e4e737bb5c170df6135a127739a9e6148ee3da82:

  Linux 5.15-rc2 (2021-09-19 17:28:22 -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.15_rc4

for you to fetch changes up to f792565326825ed806626da50c6f9a928f1079c1:

  perf/core: fix userpage->time_enabled of inactive events (2021-10-01 13:57:54 +0200)

----------------------------------------------------------------
- Make sure the destroy callback is reset when a event initialization fails

- Update the event constraints for Icelake

- Make sure the active time of an event is updated even for inactive events

----------------------------------------------------------------
Anand K Mistry (1):
      perf/x86: Reset destroy callback on event init failure

Kan Liang (1):
      perf/x86/intel: Update event constraints for ICX

Song Liu (1):
      perf/core: fix userpage->time_enabled of inactive events

 arch/x86/events/core.c       |  1 +
 arch/x86/events/intel/core.c |  1 +
 include/linux/perf_event.h   |  4 +++-
 kernel/events/core.c         | 34 ++++++++++++++++++++++++++++++----
 4 files changed, 35 insertions(+), 5 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

             reply	other threads:[~2021-10-03  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  9:55 Borislav Petkov [this message]
2021-10-03 18:20 ` [GIT PULL] perf/urgent for v5.15-rc4 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=YVl+FSNMK3BSy9gd@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