From: Arnaldo Melo <arnaldo.melo@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>, Jiebin Sun <jiebin.sun@intel.com>
Cc: acme@kernel.org, mingo@redhat.com, peterz@infradead.org,
adrian.hunter@intel.com, alexander.shishkin@linux.intel.com,
irogers@google.com, james.clark@linaro.org, jolsa@kernel.org,
mark.rutland@arm.com, dapeng1.mi@linux.intel.com,
thomas.falcon@intel.com, tianyou.li@intel.com,
wangyang.guo@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] perf c2c: Add function-view stdio support and coverage
Date: Sat, 29 Aug 2026 19:51:19 -0300 [thread overview]
Message-ID: <DF86375C-B678-4A90-AC35-0E11F9414A09@gmail.com> (raw)
In-Reply-To: <apM7dIdexptTo-1M@google.com>
On August 29, 2026 5:05:08 PM GMT-03:00, Namhyung Kim <namhyung@kernel.org> wrote:
>Hello,
>
>On Fri, Aug 21, 2026 at 01:56:07PM +0800, Jiebin Sun wrote:
>> The recently merged function-view series added an interactive TUI for
>> examining the c2c data as:
>>
>> read-side function -> contending writer -> shared cacheline
>>
>> This follow-up makes the same view available to builds without SLANG and
>> to pipes and scripts. `perf c2c report --function` now implies stdio and
>> prints the three-level hierarchy fully expanded. It requires `iaddr` in
>> the coalescing fields and is rejected together with `--stats`.
>>
>> The first two patches fix adjacent pre-existing issues: the documented
>> default coalesce fields are stale, and a workload recording failure in
>> the existing c2c shell test is incorrectly reported as a pass. The third
>> patch adds the stdio function view, and the final patch adds automated
>> coverage using a separate contended futex workload. Systems that record
>> no contended samples report a skip for the hierarchy checks rather than a
>> spurious failure.
>>
>> This series follows the function-view work merged from:
>>
>> https://lore.kernel.org/linux-perf-users/20260817094623.3288456-1-jiebin.sun@intel.com/
>>
>> The series is based on perf-tools-next commit 9453bc6a69ef ("perf vendor
>> events arm64: Fix Tegra410 Olympus event 0x0197").
>>
>> Tested with:
>>
>> - SLANG and NO_SLANG=1 builds
>> - perf test c2c
>> - perf test 'import perf'
>> - checkpatch.pl --strict on each patch
>> - unresolved-symbol checks on the Python perf module
>>
>> Jiebin Sun (4):
>> perf c2c: Fix documented default coalesce fields
>> perf tests c2c: Report skip when the workload fails
>> perf c2c: Add stdio support for the function view
>> perf tests c2c: Add function view stdio coverage
>
>Thanks for doing this!
>
>Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, I'll try and process this RSN so that the other patchset that Namhyung mentioned may conflict this can be rebased.
- Arnaldo
- Arnaldo
>
>Thanks,
>Namhyung
>
>>
>> tools/perf/Documentation/perf-c2c.txt | 14 +++-
>> tools/perf/builtin-c2c.c | 85 +++++++++++++++++--
>> tools/perf/tests/shell/c2c.sh | 114 ++++++++++++++++++++++++++
>> tools/perf/util/c2c-function.c | 9 +-
>> tools/perf/util/c2c.h | 1 +
>> 5 files changed, 205 insertions(+), 18 deletions(-)
>>
>>
>> base-commit: 9453bc6a69ef43755f1c28d5688cacdd69fa16bd
>> --
>> 2.52.0
- Arnaldo
prev parent reply other threads:[~2026-08-29 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 5:56 Jiebin Sun
2026-08-21 5:56 ` [PATCH 1/4] perf c2c: Fix documented default coalesce fields Jiebin Sun
2026-08-21 5:56 ` [PATCH 2/4] perf tests c2c: Report skip when the workload fails Jiebin Sun
2026-08-21 5:56 ` [PATCH 3/4] perf c2c: Add stdio support for the function view Jiebin Sun
2026-08-21 5:56 ` [PATCH 4/4] perf tests c2c: Add function view stdio coverage Jiebin Sun
2026-08-29 20:05 ` [PATCH 0/4] perf c2c: Add function-view stdio support and coverage Namhyung Kim
2026-08-29 22:51 ` Arnaldo Melo [this message]
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=DF86375C-B678-4A90-AC35-0E11F9414A09@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jiebin.sun@intel.com \
--cc=jolsa@kernel.org \
--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 \
--cc=thomas.falcon@intel.com \
--cc=tianyou.li@intel.com \
--cc=wangyang.guo@intel.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
all inboxes | Powered by JetHome®