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>,
	Changbin Du <changbin.du@huawei.com>, Hao Luo <haoluo@google.com>,
	Ian Rogers <irogers@google.com>,
	James Clark <james.clark@arm.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Roman Lozko <lozko.roma@gmail.com>,
	Stephane Eranian <eranian@google.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools changes for v6.4: 2nd attempt
Date: Fri,  5 May 2023 20:08:31 -0300	[thread overview]
Message-ID: <20230505230831.1084855-1-acme@kernel.org> (raw)

Hi Linus,

	Please see if this is now ok, otherwise holler and we'll try
again to address whatever problems remain,

Best regards,

- Arnaldo

The following changes since commit 1f85d016768ff19f060f3cce014a43c761de8259:

  perf test record+probe_libc_inet_pton: Fix call chain match on x86_64 (2023-05-03 11:02:21 -0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-for-v6.4-2-2023-05-05

for you to fetch changes up to 6c73f819b6b6d6f052e8dbe3f66f0693554ddf48:

  perf metrics: Fix SEGV with --for-each-cgroup (2023-05-05 19:18:55 -0300)

----------------------------------------------------------------
Additional fixes on top of the previous v6.4 perf tools pull request:

- Remove the use of bpftool to generate a vmlinux.h file to be used when
  building BPF bytecode that enables perf tools features.

  Instead add a vmlinux.h file with just the set of structs and fields
  used in the tools/perf/util/bpf_skel/*.bpf.c files and rely on libbpf's
  CO-RE functionality to compare the BTF info generated by clang for the
  BPF target against the BPF info for the kernel where the resulting tool
  runs to adjust it before loading into the kernel.

- Fix 'perf stat -b <prog id>' to match counter values obtained via
  'bpftool prog profile <prog id>', as fentry/fexit progs gets loaded,
  but the corresponding perf event wasn't being enabled and added into
  the events BPF map.

- Fix copy of 'perf stat' metric threshold to avoid SEGV on using
  uninitialized memory.

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

----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
      perf bpf skels: Stop using vmlinux.h generated from BTF, use subset of used structs + CO-RE

Dmitrii Dolgov (1):
      perf stat: Separate bperf from bpf_profiler

Ian Rogers (1):
      perf metrics: Fix SEGV with --for-each-cgroup

 tools/perf/Makefile.perf            |  20 +----
 tools/perf/builtin-stat.c           |   4 +-
 tools/perf/util/bpf_skel/.gitignore |   1 -
 tools/perf/util/bpf_skel/vmlinux.h  | 173 ++++++++++++++++++++++++++++++++++++
 tools/perf/util/evsel.h             |   5 ++
 tools/perf/util/metricgroup.c       |   1 +
 6 files changed, 182 insertions(+), 22 deletions(-)
 create mode 100644 tools/perf/util/bpf_skel/vmlinux.h

             reply	other threads:[~2023-05-05 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 23:08 Arnaldo Carvalho de Melo [this message]
2023-05-07 19:15 ` [GIT PULL] perf tools changes for v6.4: 2nd attempt 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=20230505230831.1084855-1-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=changbin.du@huawei.com \
    --cc=eranian@google.com \
    --cc=haoluo@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kcarcia@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lozko.roma@gmail.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --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).