From: sashiko-bot@kernel.org
To: "Shrikanth Hegde" <sshegde@linux.ibm.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/5] perf: Use cpumask_intersects where applicable
Date: Wed, 11 Nov 2026 08:20:41 +0000 [thread overview]
Message-ID: <sashiko-outbox-208591@kernel.org> (raw)
In-Reply-To: <20261111075945.3930230-4-sshegde@linux.ibm.com>
> cpumask_any_and returns, usually the first cpu in the intersection
> of the two cpumasks. However, if the returned value is not used or
> only to check it against nr_cpu_ids, that implies whether the two
> cpumask have a bit in common. i.e cpumask_intersects.
>
> cpumask_any_and uses ffs on (addr1[idx] & addr2[idx]) whereas
> cpumask_intersects checks only (addr1[idx] & addr2[idx]).
>
> So replace such occurrences.
>
> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111075945.3930230-1-sshegde@linux.ibm.com?part=3
next prev parent reply other threads:[~2026-11-11 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 7:59 [PATCH 0/5] cpumask: Use cpumask_intersects* APIs where applicable Shrikanth Hegde
2026-11-11 7:59 ` [PATCH 1/5] sched/rt: cpupri_find: Use cpumask_intersects " Shrikanth Hegde
2026-11-11 8:06 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 2/5] cpu/hotplug: " Shrikanth Hegde
2026-11-11 8:09 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 3/5] perf: " Shrikanth Hegde
2026-11-11 8:20 ` sashiko-bot [this message]
2026-11-11 7:59 ` [PATCH 4/5] cpuidle: Use cpumask_intersects_and " Shrikanth Hegde
2026-11-11 8:03 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 5/5] arch_topology: Use cpumask_intersects " Shrikanth Hegde
2026-11-11 8:03 ` sashiko-bot
2026-11-11 10:20 ` Sudeep Holla
2026-11-11 9:16 ` [PATCH 0/5] cpumask: Use cpumask_intersects* APIs " Peter Zijlstra
2026-11-11 9:22 ` Shrikanth Hegde
2026-11-11 10:10 ` Peter Zijlstra
2026-11-12 7:09 ` Shrikanth Hegde
2026-11-11 16:38 ` Yury Norov
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-208591@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sshegde@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.