[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2839608b-4176-2d28-f110-8923d309d9e4@meta.com>
Date: Mon, 12 Jun 2023 08:22:51 -0700
From: Yonghong Song <yhs@...a.com>
To: David Vernet <void@...ifault.com>, bpf@...r.kernel.org
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, song@...nel.org, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, linux-kernel@...r.kernel.org,
kernel-team@...a.com, tj@...nel.org
Subject: Re: [PATCH bpf-next 4/5] selftests/bpf: Update bpf_cpumask_any* tests
to use bpf_cpumask_any_distribute*
On 6/9/23 8:50 PM, David Vernet wrote:
> In a prior patch, we removed the bpf_cpumask_any() and
> bpf_cpumask_any_and() kfuncs, and replaced them with
> bpf_cpumask_any_distribute() and bpf_cpumask_any_distribute_and().
> The advertised semantics between the two kfuncs were identical, with the
> former always returning the first CPU, and the latter actually returning
> any CPU.
>
> This patch updates the selftests for these kfuncs to use the new names.
>
> Signed-off-by: David Vernet <void@...ifault.com>
Acked-by: Yonghong Song <yhs@...com>
Powered by blists - more mailing lists