From: Jiri Olsa <olsajiri@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
Song Liu <songliubraving@fb.com>, Hao Luo <haoluo@google.com>,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
Blake Jones <blakejones@google.com>
Subject: Re: [RFC 0/4] perf record: Implement off-cpu profiling with BPF (v1)
Date: Fri, 22 Apr 2022 12:11:32 +0200 [thread overview]
Message-ID: <YmJ/VAt2yblZC9HN@krava> (raw)
In-Reply-To: <20220422053401.208207-1-namhyung@kernel.org>
On Thu, Apr 21, 2022 at 10:33:57PM -0700, Namhyung Kim wrote:
SNIP
> The perf bench sched messaging created 400 processes to send/receive
> messages through unix sockets. It spent a large portion of cpu cycles
> for audit filter and read/copy the messages while most of the
> offcpu-time was in read and write calls.
>
> You can get the code from 'perf/offcpu-v1' branch in my tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>
> Enjoy! :)
CC builtin-record.o
builtin-record.c:52:10: fatal error: util/off_cpu.h: No such file or directory
52 | #include "util/off_cpu.h"
forgot to add util/off_cpu.h ?
jirka
>
> Thanks,
> Namhyung
>
>
> Namhyung Kim (4):
> perf report: Do not extend sample type of bpf-output event
> perf record: Enable off-cpu analysis with BPF
> perf record: Implement basic filtering for off-cpu
> perf record: Handle argument change in sched_switch
>
> tools/perf/Makefile.perf | 1 +
> tools/perf/builtin-record.c | 21 ++
> tools/perf/util/Build | 1 +
> tools/perf/util/bpf_off_cpu.c | 301 +++++++++++++++++++++++++
> tools/perf/util/bpf_skel/off_cpu.bpf.c | 214 ++++++++++++++++++
> tools/perf/util/evsel.c | 4 +-
> 6 files changed, 540 insertions(+), 2 deletions(-)
> create mode 100644 tools/perf/util/bpf_off_cpu.c
> create mode 100644 tools/perf/util/bpf_skel/off_cpu.bpf.c
>
>
> base-commit: 41204da4c16071be9090940b18f566832d46becc
> --
> 2.36.0.rc2.479.g8af0fa9b8e-goog
>
next prev parent reply other threads:[~2022-04-22 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 5:33 [RFC 0/4] perf record: Implement off-cpu profiling with BPF (v1) Namhyung Kim
2022-04-22 5:33 ` [PATCH 1/4] perf report: Do not extend sample type of bpf-output event Namhyung Kim
2022-04-22 5:33 ` [PATCH 2/4] perf record: Enable off-cpu analysis with BPF Namhyung Kim
2022-04-22 5:34 ` [PATCH 3/4] perf record: Implement basic filtering for off-cpu Namhyung Kim
2022-04-22 5:34 ` [PATCH 4/4] perf record: Handle argument change in sched_switch Namhyung Kim
2022-04-22 10:11 ` Jiri Olsa [this message]
2022-04-22 14:53 ` [RFC 0/4] perf record: Implement off-cpu profiling with BPF (v1) Namhyung Kim
2022-04-22 10:20 ` Milian Wolff
2022-04-22 15:01 ` Namhyung Kim
2022-04-22 19:04 ` Arnaldo Carvalho de Melo
2022-04-25 12:42 ` Milian Wolff
2022-04-25 16:49 ` Ian Rogers
2022-04-25 18:58 ` Namhyung Kim
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=YmJ/VAt2yblZC9HN@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=blakejones@google.com \
--cc=bpf@vger.kernel.org \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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).