Linux Perf Users
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Perf events updates for v6.0
Date: Mon, 1 Aug 2022 16:42:22 +0200	[thread overview]
Message-ID: <YufmTs3WbIcjlfyV@gmail.com> (raw)

Linus,

Please pull the latest perf/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-2022-08-01

   # HEAD: 326ecc15c61c349cd49d1700ff9e3e31c6fd1cd5 perf/x86/ibs: Add new IBS register bits into header

Perf events updates for this cycle are:

- Fix Intel Alder Lake PEBS memory access latency & data source profiling info bugs.

- Use Intel large-PEBS hardware feature in more circumstances, to reduce
  PMI overhead & reduce sampling data.

- Extend the lost-sample profiling output with the PERF_FORMAT_LOST ABI variant,
  which tells tooling the exact number of samples lost.

- Add new IBS register bits definitions.

- AMD uncore events: Add PerfMonV2 DF (Data Fabric) enhancements.

 Thanks,

	Ingo

------------------>
Kan Liang (2):
      perf/x86/intel: Fix PEBS memory access info encoding for ADL
      perf/x86/intel: Fix PEBS data source encoding for ADL

Like Xu (1):
      x86/events/intel/ds: Enable large PEBS for PERF_SAMPLE_WEIGHT_TYPE

Namhyung Kim (1):
      perf/core: Add a new read format to get a number of lost samples

Ravi Bangoria (1):
      perf/x86/ibs: Add new IBS register bits into header

Sandipan Das (5):
      perf/x86/amd/uncore: Use dynamic events array
      perf/x86/amd/uncore: Use attr_update for format attributes
      perf/x86/amd/uncore: Detect available DF counters
      perf/x86/amd/uncore: Add PerfMonV2 DF event format
      perf/x86/amd/uncore: Add PerfMonV2 RDPMC assignments


 arch/x86/events/amd/uncore.c      | 146 +++++++++++++++++++++++++++++++-------
 arch/x86/events/intel/core.c      |   7 +-
 arch/x86/events/intel/ds.c        | 129 ++++++++++++++++++++++-----------
 arch/x86/events/perf_event.h      |  17 ++++-
 arch/x86/include/asm/amd-ibs.h    |  16 +++--
 arch/x86/include/asm/perf_event.h |  16 +++++
 include/linux/perf_event.h        |   2 +
 include/uapi/linux/perf_event.h   |   5 +-
 kernel/events/core.c              |  21 +++++-
 kernel/events/ring_buffer.c       |   5 +-
 10 files changed, 280 insertions(+), 84 deletions(-)

             reply	other threads:[~2022-08-01 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 14:42 Ingo Molnar [this message]
2022-08-01 19:55 ` [GIT PULL] Perf events updates for v6.0 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=YufmTs3WbIcjlfyV@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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