From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 4/4] perf test tool_pmu: Add memory, network and schedstat tests
Date: Fri, 13 Nov 2026 23:45:20 +0000 [thread overview]
Message-ID: <sashiko-outbox-213872@kernel.org> (raw)
In-Reply-To: <20261113233739.3626499-5-irogers@google.com>
> Extend the Tool PMU unit test suite with subtests covering:
> - Per-process, multi-threaded Tgid deduplication, and system-wide reading
> of memory events (smaps_rollup and statm).
> - Per-process open rejection (-EINVAL) and synthetic /proc/net/dev
> parsing (including space-padded and unpadded columns) across
> enable/disable transitions for network events.
> - Per-process open rejection (-EINVAL) and per-CPU synthetic
> /proc/schedstat delta accumulation across enable/disable transitions
> for schedstat events.
> - Mixed CPU-map tool groups ({schedstat_yield,net_rx_bytes} and
> {net_rx_bytes,schedstat_yield}) across evlist__enable() and
> evlist__disable().
>
> Signed-off-by: Ian Rogers <irogers@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113233739.3626499-1-irogers@google.com?part=4
prev parent reply other threads:[~2026-11-13 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:37 [PATCH v2 0/4] perf tool_pmu: Add procfs memory, network and schedstat events Ian Rogers
2026-11-13 23:37 ` [PATCH v2 1/4] perf tool_pmu: Add memory events Ian Rogers
2026-11-14 0:05 ` sashiko-bot
2026-11-13 23:37 ` [PATCH v2 2/4] perf tool_pmu: Add network events Ian Rogers
2026-11-13 23:59 ` sashiko-bot
2026-11-13 23:37 ` [PATCH v2 3/4] perf tool_pmu: Add schedstat events Ian Rogers
2026-11-13 23:51 ` sashiko-bot
2026-11-13 23:37 ` [PATCH v2 4/4] perf test tool_pmu: Add memory, network and schedstat tests Ian Rogers
2026-11-13 23:45 ` sashiko-bot [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=sashiko-outbox-213872@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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