All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Clark Williams <williams@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ali Saidi <alisaidi@amazon.com>,
	Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
	German Gomez <german.gomez@arm.com>,
	Ian Rogers <irogers@google.com>, Leo Yan <leo.yan@linaro.org>,
	Michael Petlan <mpetlan@redhat.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Zhengjun Xing <zhengjun.xing@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools fixes for v5.19: 1st batch
Date: Sun, 19 Jun 2022 16:32:40 -0300	[thread overview]
Message-ID: <20220619193240.802856-1-acme@kernel.org> (raw)

Hi Linus,

	Please consider pulling, there are some more header sync
activity for next week, still recovering the french no-mask bonanza and
the brazilian omicron crash (maybe related?) (yeah, me+wife+kid
infected), sigh.

Best regards,

- Arnaldo

The following changes since commit 354c6e071be986a44b956f7b57f1884244431048:

  Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2022-06-18 21:51:12 -0500)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v5.19-2022-06-19

for you to fetch changes up to 140cd9ec8fdddc0e2d1684e6b69bcd05efbc9549:

  tools headers UAPI: Sync linux/prctl.h with the kernel sources (2022-06-19 11:42:25 -0300)

----------------------------------------------------------------
perf tool fixes for v5.19, 1st batch:

- Don't set data source if it's not a memory operation in ARM SPE (Statistical
  Profiling Extensions).

- Fix handling of exponent floating point values in perf stat expressions.

- Don't leak fd on failure on libperf open.

- Fix 'perf test' CPU topology test for PPC guest systems.

- Fix undefined behaviour on breakpoint account 'perf test' entry.

- Record only user callchains on the "Check ARM64 callgraphs are complete in FP
  mode" 'perf test' entry.

- Fix "perf stat CSV output linter" test on s390.

- Sync batch of kernel headers with tools/perf/.

Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

----------------------------------------------------------------
Arnaldo Carvalho de Melo (4):
      perf beauty: Update copy of linux/socket.h with the kernel sources
      tools headers UAPI: Sync x86's asm/kvm.h with the kernel sources
      tools headers arm64: Sync arm64's cputype.h with the kernel sources
      tools headers UAPI: Sync linux/prctl.h with the kernel sources

Athira Rajeev (1):
      perf test topology: Use !strncmp(right platform) to fix guest PPC comparision check

Ian Rogers (5):
      perf unwind: Fix uninitialized variable
      libperf evsel: Open shouldn't leak fd on failure
      perf test: Fix variable length array undefined behavior in bp_account
      perf expr: Allow exponents on floating point values
      perf metrics: Ensure at least 1 id per metric

Leo Yan (1):
      perf arm-spe: Don't set data source if it's not a memory operation

Michael Petlan (1):
      perf test: Record only user callchains on the "Check Arm64 callgraphs are complete in fp mode" test

Thomas Richter (1):
      perf test: Fix "perf stat CSV output linter" test on s390

 tools/arch/arm64/include/asm/cputype.h             | 12 +++-
 tools/arch/x86/include/uapi/asm/kvm.h              | 11 ++--
 tools/include/uapi/linux/prctl.h                   |  9 +++
 tools/lib/perf/evsel.c                             | 17 ++++--
 tools/perf/tests/bp_account.c                      | 16 ++++-
 tools/perf/tests/expr.c                            |  2 +
 tools/perf/tests/shell/lib/perf_csv_output_lint.py | 48 ---------------
 tools/perf/tests/shell/stat+csv_output.sh          | 69 ++++++++++++++--------
 tools/perf/tests/shell/test_arm_callgraph_fp.sh    |  2 +-
 tools/perf/tests/topology.c                        |  2 +-
 tools/perf/trace/beauty/include/linux/socket.h     |  7 ++-
 tools/perf/util/arm-spe.c                          | 22 +++----
 tools/perf/util/expr.l                             |  2 +-
 tools/perf/util/metricgroup.c                      |  9 +++
 tools/perf/util/unwind-libunwind-local.c           |  2 +-
 15 files changed, 125 insertions(+), 105 deletions(-)
 delete mode 100644 tools/perf/tests/shell/lib/perf_csv_output_lint.py

             reply	other threads:[~2022-06-19 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 19:32 Arnaldo Carvalho de Melo [this message]
2022-06-20  4:22 ` [GIT PULL] perf tools fixes for v5.19: 1st batch Arnaldo Carvalho de Melo

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=20220619193240.802856-1-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=alisaidi@amazon.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=german.gomez@arm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tmricht@linux.ibm.com \
    --cc=williams@redhat.com \
    --cc=zhengjun.xing@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.