linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Clark Williams <williams@redhat.com>,
	Kate Carcia <kcarcia@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
	Disha Goel <disgoel@linux.vnet.ibm.com>,
	Ian Rogers <irogers@google.com>,
	Jing Zhang <renyu.zj@linux.alibaba.com>,
	Xing Zhengjun <zhengjun.xing@linux.intel.com>,
	Yi Ammy <ammy.yi@intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools changes for v6.0: 5th batch
Date: Thu, 29 Sep 2022 21:33:16 -0300	[thread overview]
Message-ID: <20220930003316.62853-1-acme@kernel.org> (raw)

Hi Linus,

	Please consider pulling,

Best regards,

- Arnaldo

The following changes since commit f76349cf41451c5c42a99f18a9163377e4b364ff:

  Linux 6.0-rc7 (2022-09-25 14:01:02 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v6.0-2022-09-29

for you to fetch changes up to 8e8bf60a675473a034ecfcb7a842b98868ed74a3:

  perf build: Fixup disabling of -Wdeprecated-declarations for the python scripting engine (2022-09-29 16:03:35 -0300)

----------------------------------------------------------------
perf tools fixes for v6.0: 5th batch

- Fail the 'perf test record' entry on error, fixing a regression where just
  setup stuff like allocating memory and not the actual things being tested failed.

- Fixup disabling of -Wdeprecated-declarations for the python scripting engine, the
  previous attempt had a brown paper bag thinko.

- Fix branch stack sampling test to include sanity check for branch filter on PowerPC.

- Update is_ignored_symbol function to match the kernel ignored list, fixing running
  the 'perf test' entry that compares resolving symbols from kallsyms to resolving from
  vmlinux.

- Augment the data source type with ARM's neoverse_spe list, the previous code
  was limited in its search resolving the data source.

- Fix some clang 5 variable set but unused cases.

- Get a perf cgroup more portably in BPF as the __builtin_preserve_enum_value builtin is
  not available in older versions of clang. In those cases we can forgo BPF's CO-RE (Compile
  Once, Run Everywhere).

- More Fixes for Intel's hybrid CPU model.

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

----------------------------------------------------------------
Arnaldo Carvalho de Melo (2):
      perf tests record: Fail the test if the 'errs' counter is not zero
      perf build: Fixup disabling of -Wdeprecated-declarations for the python scripting engine

Athira Rajeev (2):
      perf tests powerpc: Fix branch stack sampling test to include sanity check for branch filter
      perf tests vmlinux-kallsyms: Update is_ignored_symbol function to match the kernel ignored list

Jing Zhang (1):
      perf arm-spe: augment the data source type with neoverse_spe list

Jiri Olsa (2):
      perf parse-events: Ignore clang 15 warning about variable set but unused in bison produced code
      perf tests mmap-basic: Remove unused variable to address clang 15 warning

Namhyung Kim (1):
      perf tools: Get a perf cgroup more portably in BPF

Zhengjun Xing (3):
      perf print-events: Fix "perf list" can not display the PMU prefix for some hybrid cache events
      perf parse-events: Remove "not supported" hybrid cache events
      perf test: Fix test case 87 ("perf record tests") for hybrid systems

 tools/perf/tests/mmap-basic.c               |  3 +--
 tools/perf/tests/perf-record.c              |  2 +-
 tools/perf/tests/shell/record.sh            |  2 +-
 tools/perf/tests/shell/test_brstack.sh      |  3 ++-
 tools/perf/tests/vmlinux-kallsyms.c         |  5 ++--
 tools/perf/util/Build                       |  2 +-
 tools/perf/util/arm-spe.c                   |  2 +-
 tools/perf/util/bpf_skel/bperf_cgroup.bpf.c | 11 +++++++-
 tools/perf/util/bpf_skel/off_cpu.bpf.c      | 18 ++++++++++---
 tools/perf/util/parse-events-hybrid.c       | 21 +++++++++++++---
 tools/perf/util/parse-events.c              | 39 +++++++++++++++++++++++++++++
 tools/perf/util/parse-events.h              |  1 +
 tools/perf/util/print-events.c              | 39 -----------------------------
 tools/perf/util/scripting-engines/Build     |  2 +-
 14 files changed, 92 insertions(+), 58 deletions(-)

             reply	other threads:[~2022-09-30  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  0:33 Arnaldo Carvalho de Melo [this message]
2022-09-30 23:05 ` [GIT PULL] perf tools changes for v6.0: 5th batch 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=20220930003316.62853-1-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=ammy.yi@intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kcarcia@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=renyu.zj@linux.alibaba.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).