linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: Howard Chu <howardchu95@gmail.com>
Cc: acme@kernel.org, peterz@infradead.org, namhyung@kernel.org,
	 mingo@redhat.com, mark.rutland@arm.com, james.clark@linaro.org,
	 alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	adrian.hunter@intel.com,  kan.liang@linux.intel.com,
	linux-perf-users@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 05/10] perf record --off-cpu: Dump off-cpu samples in BPF
Date: Mon, 11 Nov 2024 09:54:27 -0800	[thread overview]
Message-ID: <CAP-5=fXDd2MUvukB6NVMN962wxjPN6_F-AxOxOUUb-uj5BVV0A@mail.gmail.com> (raw)
In-Reply-To: <20241108204137.2444151-6-howardchu95@gmail.com>

On Fri, Nov 8, 2024 at 12:41 PM Howard Chu <howardchu95@gmail.com> wrote:
>
> Collect tid, period, callchain, and cgroup id and dump them when off-cpu
> time threshold is reached.
>
> We don't collect the off-cpu time twice (the delta), it's either in
> direct samples, or accumulated samples that are dumped at the end of
> perf.data.
>
> Suggested-by: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Howard Chu <howardchu95@gmail.com>
> ---
>  tools/perf/util/bpf_skel/off_cpu.bpf.c | 83 ++++++++++++++++++++++++--
>  1 file changed, 78 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/util/bpf_skel/off_cpu.bpf.c b/tools/perf/util/bpf_skel/off_cpu.bpf.c
> index dc6acafb9353..bf652c30b1c9 100644
> --- a/tools/perf/util/bpf_skel/off_cpu.bpf.c
> +++ b/tools/perf/util/bpf_skel/off_cpu.bpf.c
> @@ -18,10 +18,18 @@
>  #define MAX_STACKS   32
>  #define MAX_ENTRIES  102400
>
> +#define MAX_CPUS  4096
> +#define MAX_OFFCPU_LEN 37
> +
> +struct stack {
> +       u64 array[MAX_STACKS];
> +};
> +
>  struct tstamp_data {
>         __u32 stack_id;
>         __u32 state;
>         __u64 timestamp;
> +       struct stack stack;
>  };
>
>  struct offcpu_key {
> @@ -39,6 +47,24 @@ struct {
>         __uint(max_entries, MAX_ENTRIES);
>  } stacks SEC(".maps");
>
> +struct offcpu_data {
> +       u64 array[MAX_OFFCPU_LEN];
> +};
> +
> +struct {
> +       __uint(type, BPF_MAP_TYPE_PERF_EVENT_ARRAY);
> +       __uint(key_size, sizeof(__u32));
> +       __uint(value_size, sizeof(__u32));
> +       __uint(max_entries, MAX_CPUS);
> +} offcpu_output SEC(".maps");

Does patch 4 build without this definition? (we're in patch 5 here). I
think this should be in patch 4.

> +
> +struct {
> +       __uint(type, BPF_MAP_TYPE_PERCPU_ARRAY);
> +       __uint(key_size, sizeof(__u32));
> +       __uint(value_size, sizeof(struct offcpu_data));
> +       __uint(max_entries, 1);
> +} offcpu_payload SEC(".maps");
> +
>  struct {
>         __uint(type, BPF_MAP_TYPE_TASK_STORAGE);
>         __uint(map_flags, BPF_F_NO_PREALLOC);
> @@ -185,6 +211,39 @@ static inline int can_record(struct task_struct *t, int state)
>         return 1;
>  }
>
> +static inline int copy_stack(struct stack *from, struct offcpu_data *to, int n)
> +{
> +       int len = 0;
> +
> +       for (int i = 0; i < MAX_STACKS && from->array[i]; ++i, ++len)
> +               to->array[n + 2 + i] = from->array[i];
> +
> +       return len;
> +}
> +

Dump is something of a generic name. Could you kernel-doc this
function to describe the behavior?

> +static int off_cpu_dump(void *ctx, struct offcpu_data *data, struct offcpu_key *key,
> +                       struct stack *stack, __u64 delta, __u64 timestamp)
> +{
> +       /* dump tid, period, callchain, and cgroup id */
> +       int n = 0, len = 0;
> +
> +       data->array[n++] = (u64)key->tgid << 32 | key->pid;
> +       data->array[n++] = delta;
> +
> +       /* data->array[n] is callchain->nr (updated later) */
> +       data->array[n + 1] = PERF_CONTEXT_USER;
> +       data->array[n + 2] = 0;
> +       len = copy_stack(stack, data, n);
> +
> +       /* update length of callchain */
> +       data->array[n] = len + 1;
> +       n += len + 2;
> +
> +       data->array[n++] = key->cgroup_id;
> +
> +       return bpf_perf_event_output(ctx, &offcpu_output, BPF_F_CURRENT_CPU, data, n * sizeof(u64));
> +}
> +
>  static int off_cpu_stat(u64 *ctx, struct task_struct *prev,
>                         struct task_struct *next, int state)
>  {
> @@ -209,6 +268,12 @@ static int off_cpu_stat(u64 *ctx, struct task_struct *prev,
>         pelem->state = state;
>         pelem->stack_id = stack_id;
>
> +       /*
> +        * If stacks are successfully collected by bpf_get_stackid(), collect them once more
> +        * in task_storage for direct off-cpu sample dumping
> +        */
> +       if (stack_id > 0 && bpf_get_stack(ctx, &pelem->stack, MAX_STACKS * sizeof(u64), BPF_F_USER_STACK)) {
> +       }

Why the empty if?

> +
>  next:
>         pelem = bpf_task_storage_get(&tstamp, next, NULL, 0);
>
> @@ -223,11 +288,19 @@ static int off_cpu_stat(u64 *ctx, struct task_struct *prev,
>                 __u64 delta = ts - pelem->timestamp;
>                 __u64 *total;
>
> -               total = bpf_map_lookup_elem(&off_cpu, &key);
> -               if (total)
> -                       *total += delta;
> -               else
> -                       bpf_map_update_elem(&off_cpu, &key, &delta, BPF_ANY);
> +               if (delta >= offcpu_thresh) {
> +                       int zero = 0;
> +                       struct offcpu_data *data = bpf_map_lookup_elem(&offcpu_payload, &zero);
> +
> +                       if (data)
> +                               off_cpu_dump(ctx, data, &key, &pelem->stack, delta, pelem->timestamp);
> +               } else {
> +                       total = bpf_map_lookup_elem(&off_cpu, &key);
> +                       if (total)
> +                               *total += delta;
> +                       else
> +                               bpf_map_update_elem(&off_cpu, &key, &delta, BPF_ANY);
> +               }

Looks good! :-)

Thanks,
Ian

>
>                 /* prevent to reuse the timestamp later */
>                 pelem->timestamp = 0;
> --
> 2.43.0
>

  reply	other threads:[~2024-11-11 17:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 20:41 [PATCH v7 00/10] perf record --off-cpu: Dump off-cpu samples directly Howard Chu
2024-11-08 20:41 ` [PATCH v7 01/10] perf record --off-cpu: Add --off-cpu-thresh option Howard Chu
2024-11-11 17:40   ` Ian Rogers
2024-11-08 20:41 ` [PATCH v7 02/10] perf evsel: Expose evsel__is_offcpu_event() for future use Howard Chu
2024-11-11 17:41   ` Ian Rogers
2024-11-08 20:41 ` [PATCH v7 03/10] perf record --off-cpu: Parse off-cpu event Howard Chu
2024-11-11 17:45   ` Ian Rogers
2024-11-11 18:10     ` Howard Chu
2024-11-08 20:41 ` [PATCH v7 04/10] perf record --off-cpu: Preparation of off-cpu BPF program Howard Chu
2024-11-11 17:47   ` Ian Rogers
2024-11-11 18:08     ` Howard Chu
2024-11-12 20:52     ` Howard Chu
2024-11-08 20:41 ` [PATCH v7 05/10] perf record --off-cpu: Dump off-cpu samples in BPF Howard Chu
2024-11-11 17:54   ` Ian Rogers [this message]
2024-11-11 18:05     ` Howard Chu
2024-11-11 18:11       ` Ian Rogers
2024-11-08 20:41 ` [PATCH v7 06/10] perf evsel: Assemble offcpu samples Howard Chu
2024-11-11 17:55   ` Ian Rogers
2024-11-08 20:41 ` [PATCH v7 07/10] perf record --off-cpu: Disable perf_event's callchain collection Howard Chu
2024-11-08 20:41 ` [PATCH v7 08/10] perf script: Display off-cpu samples correctly Howard Chu
2024-11-11 17:56   ` Ian Rogers
2024-11-08 20:41 ` [PATCH v7 09/10] perf record --off-cpu: Dump the remaining samples in BPF's stack trace map Howard Chu
2024-11-11 18:06   ` Ian Rogers
2024-11-12 21:40     ` Howard Chu
2024-11-08 20:41 ` [PATCH v7 10/10] perf test: Add direct off-cpu test Howard Chu
2024-11-11 18:08   ` Ian Rogers
2024-11-12 18:39 ` [PATCH v7 00/10] perf record --off-cpu: Dump off-cpu samples directly Arnaldo Carvalho de Melo
2024-11-12 18:59   ` Ian Rogers
2024-11-12 19:17   ` Arnaldo Carvalho de Melo
2024-11-12 19:18     ` Arnaldo Carvalho de Melo
2024-11-12 19:18       ` Arnaldo Carvalho de Melo
2024-11-12 19:32         ` Arnaldo Carvalho de Melo
2024-11-12 19:56     ` Arnaldo Carvalho de Melo
2024-11-12 20:03       ` Howard Chu
2024-11-16 14:42       ` Howard Chu

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='CAP-5=fXDd2MUvukB6NVMN962wxjPN6_F-AxOxOUUb-uj5BVV0A@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=howardchu95@gmail.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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).