From: Milian Wolff <milian.wolff@kdab.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Cc: 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:20:45 +0200 [thread overview]
Message-ID: <35121321.B44TWeBT9p@milian-workstation> (raw)
In-Reply-To: <20220422053401.208207-1-namhyung@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
On Freitag, 22. April 2022 07:33:57 CEST Namhyung Kim wrote:
> Hello,
>
> This is the first version of off-cpu profiling support. Together with
> (PMU-based) cpu profiling, it can show holistic view of the performance
> characteristics of your application or system.
Hey Namhyung,
this is awesome news! In hotspot, I've long done off-cpu profiling manually by
looking at the time between --switch-events. The downside is that we also need
to track the sched:sched_switch event to get a call stack. But this approach
also works with dwarf based unwinding, and also includes kernel stacks.
> With BPF, it can aggregate scheduling stats for interested tasks
> and/or states and convert the data into a form of perf sample records.
> I chose the bpf-output event which is a software event supposed to be
> consumed by BPF programs and renamed it as "offcpu-time". So it
> requires no change on the perf report side except for setting sample
> types of bpf-output event.
>
> Basically it collects userspace callstack for tasks as it's what users
> want mostly. Maybe we can add support for the kernel stacks but I'm
> afraid that it'd cause more overhead. So the offcpu-time event will
> always have callchains regardless of the command line option, and it
> enables the children mode in perf report by default.
Has anything changed wrt perf/bpf and user applications not compiled with `-
fno-omit-frame-pointer`? I.e. does this new utility only work for specially
compiled applications, or do we also get backtraces for "normal" binaries that
we can install through package managers?
Thanks
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5272 bytes --]
next prev parent reply other threads:[~2022-04-22 10:26 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 ` [RFC 0/4] perf record: Implement off-cpu profiling with BPF (v1) Jiri Olsa
2022-04-22 14:53 ` Namhyung Kim
2022-04-22 10:20 ` Milian Wolff [this message]
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=35121321.B44TWeBT9p@milian-workstation \
--to=milian.wolff@kdab.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