From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org,
Song Liu <songliubraving@fb.com>, Hao Luo <haoluo@google.com>,
Milian Wolff <milian.wolff@kdab.com>,
bpf@vger.kernel.org, Blake Jones <blakejones@google.com>
Subject: Re: [PATCH 1/6] perf offcpu: Fix a build failure on old kernels
Date: Tue, 28 Jun 2022 11:44:46 -0300 [thread overview]
Message-ID: <YrsT3iw+FEXb6kxF@kernel.org> (raw)
In-Reply-To: <20220624231313.367909-2-namhyung@kernel.org>
Em Fri, Jun 24, 2022 at 04:13:08PM -0700, Namhyung Kim escreveu:
> Old kernels have task_struct which contains "state" field and newer
> kernels have "__state". While the get_task_state() in the BPF code
> handles that in some way, it assumed the current kernel has the new
> definition and it caused a build error on old kernels.
>
> We should not assume anything and access them carefully. Do not use
> the task struct directly and access them using new and old definitions
> in a row.
I added a:
Fixes: edc41a1099c2d08c ("perf record: Enable off-cpu analysis with BPF")
Ok?
- Arnaldo
> Reported-by: Ian Rogers <irogers@google.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/util/bpf_skel/off_cpu.bpf.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/util/bpf_skel/off_cpu.bpf.c b/tools/perf/util/bpf_skel/off_cpu.bpf.c
> index 792ae2847080..cc6d7fd55118 100644
> --- a/tools/perf/util/bpf_skel/off_cpu.bpf.c
> +++ b/tools/perf/util/bpf_skel/off_cpu.bpf.c
> @@ -71,6 +71,11 @@ struct {
> __uint(max_entries, 1);
> } cgroup_filter SEC(".maps");
>
> +/* new kernel task_struct definition */
> +struct task_struct___new {
> + long __state;
> +} __attribute__((preserve_access_index));
> +
> /* old kernel task_struct definition */
> struct task_struct___old {
> long state;
> @@ -93,14 +98,17 @@ const volatile bool uses_cgroup_v1 = false;
> */
> static inline int get_task_state(struct task_struct *t)
> {
> - if (bpf_core_field_exists(t->__state))
> - return BPF_CORE_READ(t, __state);
> + /* recast pointer to capture new type for compiler */
> + struct task_struct___new *t_new = (void *)t;
>
> - /* recast pointer to capture task_struct___old type for compiler */
> - struct task_struct___old *t_old = (void *)t;
> + if (bpf_core_field_exists(t_new->__state)) {
> + return BPF_CORE_READ(t_new, __state);
> + } else {
> + /* recast pointer to capture old type for compiler */
> + struct task_struct___old *t_old = (void *)t;
>
> - /* now use old "state" name of the field */
> - return BPF_CORE_READ(t_old, state);
> + return BPF_CORE_READ(t_old, state);
> + }
> }
>
> static inline __u64 get_cgroup_id(struct task_struct *t)
> --
> 2.37.0.rc0.161.g10f37bed90-goog
--
- Arnaldo
next prev parent reply other threads:[~2022-06-28 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 23:13 [PATCHSET 0/6] perf tools: A couple of fixes for perf record --off-cpu (v1) Namhyung Kim
2022-06-24 23:13 ` [PATCH 1/6] perf offcpu: Fix a build failure on old kernels Namhyung Kim
2022-06-28 14:44 ` Arnaldo Carvalho de Melo [this message]
2022-06-28 16:52 ` Namhyung Kim
2022-06-24 23:13 ` [PATCH 2/6] perf offcpu: Accept allowed sample types only Namhyung Kim
2022-06-28 14:46 ` Arnaldo Carvalho de Melo
2022-06-24 23:13 ` [PATCH 3/6] perf offcpu: Check process id for the given workload Namhyung Kim
2022-06-24 23:13 ` [PATCH 4/6] perf offcpu: Parse process id separately Namhyung Kim
2022-06-24 23:13 ` [PATCH 5/6] perf offcpu: Track child processes Namhyung Kim
2022-06-24 23:13 ` [PATCH 6/6] perf offcpu: Update offcpu test for child process Namhyung Kim
2022-06-28 14:40 ` [PATCHSET 0/6] perf tools: A couple of fixes for perf record --off-cpu (v1) Arnaldo Carvalho de Melo
2022-06-28 16:51 ` 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=YrsT3iw+FEXb6kxF@kernel.org \
--to=acme@kernel.org \
--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=milian.wolff@kdab.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.