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>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	Ian Rogers <irogers@google.com>, Song Liu <songliubraving@fb.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools fixes for v5.16: 2nd batch
Date: Tue,  7 Dec 2021 10:44:07 -0300	[thread overview]
Message-ID: <20211207134407.297788-1-acme@kernel.org> (raw)

Hi Linus,

	Please consider pulling,

Best regards,

- Arnaldo

The following changes since commit cd8c917a56f20f48748dd43d9ae3caff51d5b987:

  Makefile: Do not quote value for CONFIG_CC_IMPLICIT_FALLTHROUGH (2021-12-06 16:42:47 -0800)

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.16-2021-12-07

for you to fetch changes up to 5a897531e00243cebbcc4dbe4ab06cd559ccf53f:

  perf bpf_skel: Do not use typedef to avoid error on old clang (2021-12-06 21:57:53 -0300)

----------------------------------------------------------------
perf tools fixes for v5.16: 2nd batch

- Fix SMT detection fast read path on sysfs.

- Fix memory leaks when processing feature headers in perf.data files.

- Fix 'Simple expression parser' 'perf test' on arch without CPU die topology
  info, such as s/390.

- Fix building perf with BUILD_BPF_SKEL=1.

- Fix 'perf bench' by reverting "perf bench: Fix two memory leaks detected with ASan".

- Fix itrace space allowed for new attributes in 'perf script'.

- Fix the build feature detection fast path, that was always failing on systems
  with python3 development packages, speeding up the build.

- Reset shadow counts before loading, fixing metrics using duration_time.

- Sync more kernel headers changed by the new futex_waitv syscall: s390 and powerpc.

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

----------------------------------------------------------------
Adrian Hunter (1):
      perf inject: Fix itrace space allowed for new attributes

Arnaldo Carvalho de Melo (3):
      tools headers UAPI: Sync s390 syscall table file changed by new futex_waitv syscall
      tools headers UAPI: Sync powerpc syscall table file changed by new futex_waitv syscall
      tools build: Remove needless libpython-version feature check that breaks test-all fast path

Ian Rogers (3):
      perf tools: Fix SMT detection fast read path
      perf test: Reset shadow counts before loading
      perf header: Fix memory leaks when processing feature headers

Jiri Olsa (1):
      Revert "perf bench: Fix two memory leaks detected with ASan"

Song Liu (2):
      perf bpf: Fix building perf with BUILD_BPF_SKEL=1 by default in more distros
      perf bpf_skel: Do not use typedef to avoid error on old clang

Thomas Richter (1):
      perf test: Fix 'Simple expression parser' test on arch without CPU die topology info

 tools/build/Makefile.feature                       |  1 -
 tools/build/feature/Makefile                       |  4 ----
 tools/build/feature/test-all.c                     |  5 -----
 tools/build/feature/test-libpython-version.c       | 11 -----------
 tools/perf/Makefile.config                         |  2 --
 tools/perf/arch/powerpc/entry/syscalls/syscall.tbl |  1 +
 tools/perf/arch/s390/entry/syscalls/syscall.tbl    |  1 +
 tools/perf/bench/sched-messaging.c                 |  4 ----
 tools/perf/builtin-inject.c                        |  2 +-
 tools/perf/tests/expr.c                            |  4 +++-
 tools/perf/tests/parse-metric.c                    |  1 +
 tools/perf/util/bpf_skel/bperf.h                   | 14 --------------
 tools/perf/util/bpf_skel/bperf_follower.bpf.c      | 19 ++++++++++++++-----
 tools/perf/util/bpf_skel/bperf_leader.bpf.c        | 19 ++++++++++++++-----
 tools/perf/util/bpf_skel/bpf_prog_profiler.bpf.c   |  2 +-
 tools/perf/util/header.c                           | 15 ++++++++++-----
 tools/perf/util/smt.c                              |  2 +-
 17 files changed, 47 insertions(+), 60 deletions(-)
 delete mode 100644 tools/build/feature/test-libpython-version.c
 delete mode 100644 tools/perf/util/bpf_skel/bperf.h

             reply	other threads:[~2021-12-07 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 13:44 Arnaldo Carvalho de Melo [this message]
2021-12-07 14:10 ` [GIT PULL] perf tools fixes for v5.16: 2nd batch Arnaldo Carvalho de Melo
2021-12-07 23:43 ` 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=20211207134407.297788-1-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@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=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    --cc=tmricht@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=williams@redhat.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).