mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hui Su <sh_def@163.com>
Cc: bpf@vger.kernel.org, qmo@kernel.org, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
	memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
	ihor.solodrai@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] bpftool: Fix sparse CPU IDs
Date: Thu, 24 Sep 2026 10:20:07 +0000	[thread overview]
Message-ID: <179024520721.1453978.11185666533780747753.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923004243.969919-1-sh_def@163.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Wed, 23 Sep 2026 09:42:41 +0900 you wrote:
> bpftool currently assumes that possible CPU IDs are dense. This is not
> true when the possible CPU mask itself is sparse, such as 0,2-3. In that
> case, per-CPU map output labels and prog profile event-array keys can
> refer to the wrong logical CPUs.
> 
> The first patch keeps dense per-CPU buffer slots separate from logical CPU
> IDs when printing per-CPU map values. The parsed CPU count is passed
> together with the logical CPU IDs so that output labels and loop bounds use
> the same possible-CPU mask.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/2] bpftool: Fix CPU IDs in per-CPU map output
    https://git.kernel.org/bpf/bpf-next/c/dbf8cef936c7
  - [bpf-next,v3,2/2] bpftool: Fix sparse CPU IDs in prog profile
    https://git.kernel.org/bpf/bpf-next/c/edc071d7b3aa

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-24 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  0:42 Hui Su
2026-09-23  0:42 ` [PATCH bpf-next v3 1/2] bpftool: Fix CPU IDs in per-CPU map output Hui Su
2026-09-23  0:42 ` [PATCH bpf-next v3 2/2] bpftool: Fix sparse CPU IDs in prog profile Hui Su
2026-09-23  1:27   ` bot+bpf-ci
2026-09-24 10:20 ` 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=179024520721.1453978.11185666533780747753.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=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    --cc=sh_def@163.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@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
all inboxes | Powered by JetHome®