[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM9d7cjFYPPusN+yGEHe5B5hwPoiLqXj=Q0DqjBaZR9gTAADTg@mail.gmail.com>
Date: Mon, 29 Apr 2024 15:06:05 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Howard Chu <howardchu95@...il.com>, peterz@...radead.org, mingo@...hat.com,
mark.rutland@....com, alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com, kan.liang@...ux.intel.com,
zegao2021@...il.com, leo.yan@...ux.dev, ravi.bangoria@....com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH v1 1/4] perf record: Dump off-cpu samples directly
On Mon, Apr 29, 2024 at 11:53 AM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> On Mon, Apr 22, 2024 at 04:36:45PM +0800, Howard Chu wrote:
> > Parse off-cpu events using parse_event(). Change the placement of
> > record__config_off_cpu to after record__open because we need to write
> > mmapped fds into BPF's perf_event_array map, also, write
> > sample_id/sample_type into BPF. In record__pushfn and record__aio_pushfn,
> > handle off-cpu samples using off_cpu_strip. This is because the off-cpu
> > samples that we want to write to perf.data is in off-cpu samples' raw_data
> > section:
>
> Hey,
>
> This lacks a cover letter and the chainig of patches so that b4
> can fetch the series.
>
> Also all 5 patches have the same summary and different
> descriptions and contents, can you please rework the patch series, using
> 'git format-patch', and make the description reflect what each patch is
> doing?
He already sent out v2.
Thanks,
Namhyung
https://lore.kernel.org/r/20240424024805.144759-1-howardchu95@gmail.com/
Powered by blists - more mailing lists