bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>, 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>, Song Liu <songliubraving@fb.com>,
	Hao Luo <haoluo@google.com>, Milian Wolff <milian.wolff@kdab.com>,
	bpf <bpf@vger.kernel.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	Blake Jones <blakejones@google.com>
Subject: Re: [PATCH 3/6] perf record: Implement basic filtering for off-cpu
Date: Wed, 25 May 2022 11:06:58 -0300	[thread overview]
Message-ID: <Yo44AppGsPKvf7Al@kernel.org> (raw)
In-Reply-To: <Yo4Wpqzwp+XmfkMV@kernel.org>

Em Wed, May 25, 2022 at 08:44:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, May 25, 2022 at 08:27:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, May 19, 2022 at 02:02:28PM -0700, Namhyung Kim escreveu:
> > > On Wed, May 18, 2022 at 9:02 PM Ian Rogers <irogers@google.com> wrote:
> > > > Perhaps more concise with a for_each:

> > > > perf_cpu_map__for_each_cpu(cpu, idx, evlist->core.user_requested_cpus)
> > > >   bpf_map_update_elem(fd, &cpu.cpu, &val, BPF_ANY);

> > So I'll wait for a new version of this patchset.

> I take that back, will apply and this can be a follow up patch, right?

I tested it and added some committer notes, everything is now at my
tmp.perf/core branch and will transition to perf/core on its way to 5.19
later today, after tests finish.

- Arnaldo

  reply	other threads:[~2022-05-25 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 22:47 [RFC 0/6] perf record: Implement off-cpu profiling with BPF (v3) Namhyung Kim
2022-05-18 22:47 ` [PATCH 1/6] perf report: Do not extend sample type of bpf-output event Namhyung Kim
2022-05-18 22:47 ` [PATCH 2/6] perf record: Enable off-cpu analysis with BPF Namhyung Kim
2022-05-19  3:58   ` Ian Rogers
2022-05-19 21:01     ` Namhyung Kim
2022-06-01  0:00   ` Ian Rogers
2022-06-01  6:01     ` Namhyung Kim
2022-06-02 22:36       ` Namhyung Kim
2022-05-18 22:47 ` [PATCH 3/6] perf record: Implement basic filtering for off-cpu Namhyung Kim
2022-05-19  4:02   ` Ian Rogers
2022-05-19 21:02     ` Namhyung Kim
2022-05-25 11:27       ` Arnaldo Carvalho de Melo
2022-05-25 11:44         ` Arnaldo Carvalho de Melo
2022-05-25 14:06           ` Arnaldo Carvalho de Melo [this message]
2022-05-18 22:47 ` [PATCH 4/6] perf record: Handle argument change in sched_switch Namhyung Kim
2022-05-19  4:04   ` Ian Rogers
2022-05-18 22:47 ` [PATCH 5/6] perf record: Add cgroup support for off-cpu profiling Namhyung Kim
2022-05-19  4:07   ` Ian Rogers
2022-05-18 22:47 ` [PATCH 6/6] perf test: Add a basic offcpu profiling test Namhyung Kim
2022-05-19  4:08   ` Ian Rogers

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=Yo44AppGsPKvf7Al@kernel.org \
    --to=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=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 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).