BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@meta.com, eddyz87@gmail.com,
	memxor@gmail.com, yatsenko@meta.com
Subject: Re: [PATCH bpf-next v4 0/3] bpftool: Improve perf counter reporting
Date: Thu, 17 Sep 2026 22:30:05 +0000	[thread overview]
Message-ID: <178968420538.152767.17236037984981874138.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916-bpftool_cyles_per_run-v4-0-f2de02c480d5@meta.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 16 Sep 2026 12:26:39 -0700 you wrote:
> Accept valid perf snapshots whose counter is zero. Group selected metrics
> per CPU so derived ratios cover the same scheduling intervals. Scale each
> per-CPU counter before aggregation and report cycles per program run.
> 
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
> ---
> Changes in v4:
> - Use enabled time to recognize valid zero-counter snapshots.
> - Build and enable each CPU's complete perf event group in one pass.
> - Keep run_cnt as the total count, drop run_cnt_valid.
> - Link to v3: https://patch.msgid.link/20260908-bpftool_cyles_per_run-v3-0-60e86f325c35@meta.com
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/3] bpftool: Accept zero perf counter snapshots
    https://git.kernel.org/bpf/bpf-next/c/b2cf39f53478
  - [bpf-next,v4,2/3] bpftool: Group profile events by CPU
    https://git.kernel.org/bpf/bpf-next/c/6b5fe4b6d5ae
  - [bpf-next,v4,3/3] bpftool: Scale counters and report cycles per run
    https://git.kernel.org/bpf/bpf-next/c/c2c8bd265627

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-17 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 19:26 [PATCH bpf-next v4 0/3] bpftool: Improve perf counter reporting Mykyta Yatsenko
2026-09-16 19:26 ` [PATCH bpf-next v4 1/3] bpftool: Accept zero perf counter snapshots Mykyta Yatsenko
2026-09-16 20:07   ` bot+bpf-ci
2026-09-16 19:26 ` [PATCH bpf-next v4 2/3] bpftool: Group profile events by CPU Mykyta Yatsenko
2026-09-16 19:26 ` [PATCH bpf-next v4 3/3] bpftool: Scale counters and report cycles per run Mykyta Yatsenko
2026-09-17 22:30 ` patchwork-bot+netdevbpf [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=178968420538.152767.17236037984981874138.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.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