From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: mingo@redhat.com, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
peterz@infradead.org, kan.liang@linux.intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
gautam@linux.ibm.com
Subject: Re: [PATCH v16 00/10] perf record --off-cpu: Dump off-cpu samples directly
Date: Mon, 5 May 2025 12:56:29 -0300 [thread overview]
Message-ID: <aBjfrUqFe444h_CF@x1> (raw)
In-Reply-To: <20250501022809.449767-1-howardchu95@gmail.com>
On Wed, Apr 30, 2025 at 07:27:58PM -0700, Howard Chu wrote:
> Changes in v16:
> - Add Tested-by from Gautam and Acked-by from Namhyung.
> - Rebase on the perf-tools-next branch.
> - Edit the commit message of patch 10.
> - Fix a bug caused by the type change of struct perf_cpu.
> - Rename test_offcpu_over_thresh() to test_offcpu_above_thresh().
Please take a look at the tmp.perf-tools-next branch at:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
I added some Committer testing with some extra steps to describe how to
reproduce the results and there is one point that I have to retest,
where there is a FIXME in the Committer testing notes, perhaps I made a
mistake or that fix should be moved to after or before some patch,
unsure.
- Arnaldo
next prev parent reply other threads:[~2025-05-05 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 2:27 [PATCH v16 00/10] perf record --off-cpu: Dump off-cpu samples directly Howard Chu
2025-05-01 2:27 ` [PATCH v16 01/10] perf evsel: Expose evsel__is_offcpu_event() for future use Howard Chu
2025-05-01 2:28 ` [PATCH v16 02/10] perf record --off-cpu: Parse off-cpu event Howard Chu
2025-05-01 2:28 ` [PATCH v16 03/10] perf record --off-cpu: Preparation of off-cpu BPF program Howard Chu
2025-05-01 2:28 ` [PATCH v16 04/10] perf record --off-cpu: Dump off-cpu samples in BPF Howard Chu
2025-05-01 2:28 ` [PATCH v16 05/10] perf evsel: Assemble offcpu samples Howard Chu
2025-05-01 2:28 ` [PATCH v16 06/10] perf record --off-cpu: Disable perf_event's callchain collection Howard Chu
2025-05-01 2:28 ` [PATCH v16 07/10] perf script: Display off-cpu samples correctly Howard Chu
2025-05-01 2:28 ` [PATCH v16 08/10] perf record --off-cpu: Dump the remaining samples in BPF's stack trace map Howard Chu
2025-05-01 2:28 ` [PATCH v16 09/10] perf record --off-cpu: Add --off-cpu-thresh option Howard Chu
2025-05-01 2:28 ` [PATCH v16 10/10] perf test: Add direct off-cpu tests Howard Chu
2025-05-01 15:13 ` [PATCH v16 00/10] perf record --off-cpu: Dump off-cpu samples directly Ian Rogers
2025-05-05 15:56 ` Arnaldo Carvalho de Melo [this message]
2025-05-06 19:48 ` Ian Rogers
[not found] ` <CA+JHD93FaugH5ny6+bBkciwoWzLN5RKCbtBq77V2bi8Rs15-UQ@mail.gmail.com>
2025-05-06 20:51 ` Ian Rogers
[not found] ` <CA+JHD935y5ky0EWrG4okShjizP9JDp1hOoUiCNT3c6WUj0k1VA@mail.gmail.com>
2025-05-14 20:15 ` Howard Chu
2025-05-15 18:20 ` 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=aBjfrUqFe444h_CF@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=gautam@linux.ibm.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--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 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.