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 Jajeev <atrajeev@linux.vnet.ibm.com>,
Dmitry Dolgov <9erthalion6@gmail.com>,
Ian Rogers <irogers@google.com>, Leo Yan <leo.yan@linaro.org>,
Mike Leach <mike.leach@linaro.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools fixes for v6.2: 2nd batch
Date: Wed, 11 Jan 2023 14:43:31 -0300 [thread overview]
Message-ID: <20230111174331.984275-1-acme@kernel.org> (raw)
Hi Linus,
Please consider pulling,
Best regards,
- Arnaldo
The following changes since commit 1fe4fd6f5cad346e598593af36caeadc4f5d4fa9:
Merge tag 'xfs-6.2-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux (2023-01-08 12:11:45 -0600)
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.2-2-2023-01-11
for you to fetch changes up to cf129830ee820f7fc90b98df193cd49d49344d09:
perf auxtrace: Fix address filter duplicate symbol selection (2023-01-11 14:03:44 -0300)
----------------------------------------------------------------
perf tools fixes for v6.2: 2nd batch
- Make 'perf kmem' cope with the removal of kmem:kmem_cache_alloc_node and
kmem:kmalloc_node in the 11e9734bcb6a7361 ("mm/slab_common: unify NUMA and
UMA version of tracepoints") commit, making sure it works with Linux >= 6.2 as well
as with older kernels where those tracepoints are present.
- Also make it handle the new "node" kmem:kmalloc and kmem:kmem_cache_alloc tracepoint
field introduced in that same commit.
- Fix hardware tracing PMU address filter duplicate symbol selection, that was
preventing to match with static functions with the same name present in different
object files.
- Fix regression on what linux/types.h file gets used to build the "BPF prologue"
'perf test' entry, the system one lacks the fmode_t definition used in this test,
so provide that type in the test itself.
- Avoid build breakage with libbpf < 0.8.0 + LIBBPF_DYNAMIC=1. If the user asks for
linking with the libbpf package provided by the distro, then it has to be >= 0.8.0.
Using the libbpf supplied with the kernel would be a fallback in that case.
- Fix the build when libbpf isn't available or explicitly disabled via NO_LIBBPF=1.
- Don't try to install libtraceevent plugins as its not anymore in the kernel sources
and will thus always fail.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
----------------------------------------------------------------
Adrian Hunter (1):
perf auxtrace: Fix address filter duplicate symbol selection
Arnaldo Carvalho de Melo (2):
perf tools: Don't install libtraceevent plugins as its not anymore in the kernel sources
perf bpf: Avoid build breakage with libbpf < 0.8.0 + LIBBPF_DYNAMIC=1
Athira Rajeev (1):
perf tests bpf prologue: Fix bpf-script-test-prologue test compile issue with clang
Ian Rogers (2):
perf build: Properly guard libbpf includes
perf build: Fix build error when NO_LIBBPF=1
Leo Yan (2):
perf kmem: Support legacy tracepoints
perf kmem: Support field "node" in evsel__process_alloc_event() coping with recent tracepoint restructuring
tools/perf/Makefile.config | 12 ++----
tools/perf/Makefile.perf | 21 ++++++----
tools/perf/builtin-kmem.c | 65 ++++++++++++++++++++++-------
tools/perf/builtin-trace.c | 2 +
tools/perf/tests/bpf-script-test-prologue.c | 2 +
tools/perf/tests/make | 12 ------
tools/perf/util/auxtrace.c | 2 +-
tools/perf/util/bpf_counter.h | 6 +++
8 files changed, 77 insertions(+), 45 deletions(-)
next reply other threads:[~2023-01-11 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 17:43 Arnaldo Carvalho de Melo [this message]
2023-01-11 23:17 ` [GIT PULL] perf tools fixes for v6.2: 2nd 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=20230111174331.984275-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=9erthalion6@gmail.com \
--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=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=tglx@linutronix.de \
--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).