mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@nvidia.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, yury.norov@gmail.com,
	linux-perf-users@vger.kernel.org, mingo@kernel.org,
	peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, tglx@kernel.org,
	sudeep.holla@kernel.org, linux@rasmusvillemoes.dk
Subject: Re: [PATCH 0/5] cpumask: Use cpumask_intersects* APIs where applicable
Date: Wed, 11 Nov 2026 11:38:38 -0500	[thread overview]
Message-ID: <avSaDpLLwOP6vl-J@yury> (raw)
In-Reply-To: <20261111075945.3930230-1-sshegde@linux.ibm.com>

On Wed, Nov 11, 2026 at 01:29:40PM +0530, Shrikanth Hegde wrote:
> It was observed while working on cpumask_intersects_and, check like
> below could use it instead.
> 
> if (cpumask_first_and_and() < nr_cpu_ids)
> 
> While there, did check the code for any such similar patterns of
> cpumask_any_and, cpumask_first_and and explicit loops where
> cpu found by these APIs are not being used. All those callsites
> instead can simply use cpumask_intersects.
> 
> Note that few more places can use similar change. But, I have left
> them as is. 
> drivers/net/ethernet/sfc/efx_channels.c+370
> drivers/net/ethernet/sfc/siena/efx_channels.c+371
> drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c+153
> 
> Also, these patches can combined into three patches if that is
> easier for review/merge. I have kept it separate since they belong
> to different subsystems.
> 
> Shrikanth Hegde (5):
>   sched/rt: cpupri_find: Use cpumask_intersects where applicable
>   cpu/hotplug: Use cpumask_intersects where applicable
>   perf: Use cpumask_intersects where applicable
>   cpuidle: Use cpumask_intersects_and where applicable
>   arch_topology: Use cpumask_intersects where applicable
 
Reviewed-by: Yury Norov <ynorov@nvidia.com>

>  drivers/base/arch_topology.c | 9 +--------
>  drivers/cpuidle/coupled.c    | 4 ++--
>  kernel/cpu.c                 | 3 +--
>  kernel/events/core.c         | 7 ++-----
>  kernel/sched/cpupri.c        | 2 +-
>  5 files changed, 7 insertions(+), 18 deletions(-)
> 
> -- 
> 2.52.0
> 

      parent reply	other threads:[~2026-11-11 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  7:59 Shrikanth Hegde
2026-11-11  7:59 ` [PATCH 1/5] sched/rt: cpupri_find: Use cpumask_intersects " Shrikanth Hegde
2026-11-11  7:59 ` [PATCH 2/5] cpu/hotplug: " Shrikanth Hegde
2026-11-11  7:59 ` [PATCH 3/5] perf: " Shrikanth Hegde
2026-11-11  7:59 ` [PATCH 4/5] cpuidle: Use cpumask_intersects_and " Shrikanth Hegde
2026-11-11  7:59 ` [PATCH 5/5] arch_topology: Use cpumask_intersects " Shrikanth Hegde
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-11 16:38 ` Yury Norov [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=avSaDpLLwOP6vl-J@yury \
    --to=ynorov@nvidia.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sshegde@linux.ibm.com \
    --cc=sudeep.holla@kernel.org \
    --cc=tglx@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=yury.norov@gmail.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

all inboxes | Powered by JetHome®