public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: kan.liang@linux.intel.com, peterz@infradead.org,
	mingo@redhat.com, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org
Cc: tglx@linutronix.de, hpa@zytor.com, sfr@canb.auug.org.au
Subject: Re: [PATCH] perf: Fix topology_sibling_cpumask check warning on ARM
Date: Thu, 12 Sep 2024 16:53:15 +0100	[thread overview]
Message-ID: <0a1f237f-281f-4a08-968f-6c6f94f0a035@arm.com> (raw)
In-Reply-To: <20240912145025.1574448-1-kan.liang@linux.intel.com>

On 12/09/2024 15:50, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
> 
> The below warning is triggered when building with arm
> multi_v7_defconfig.
> 
> kernel/events/core.c: In function 'perf_event_setup_cpumask':
> kernel/events/core.c:14012:13: warning: the comparison will always
> evaluate as 'true' for the address of 'thread_sibling' will never be
> NULL [-Waddress]
> 14012 |         if (!topology_sibling_cpumask(cpu)) {
> 
> The perf_event_init_cpu() may be invoked at the early boot stage, while
> the topology_*_cpumask hasn't been initialized yet. The check is to
> specially handle the case, and initialize the perf_online_<domain>_masks
> on the boot CPU.
> X86 uses a per-cpu cpumask pointer, which could be NULL at the early
> boot stage. However, ARM uses a global variable, which never be NULL.
> 
> Use perf_online_mask as an indicator instead. Only initialize the
> perf_online_<domain>_masks when perf_online_mask is empty.
> 
> Fix a typo as well.
> 
> Fixes: 4ba4f1afb6a9 ("perf: Generic hotplug support for a PMU with a scope")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/lkml/20240911153854.240bbc1f@canb.auug.org.au/
> Reported-by: Steven Price <steven.price@arm.com>
> Closes: https://lore.kernel.org/lkml/1835eb6d-3e05-47f3-9eae-507ce165c3bf@arm.com/
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>

Tested-by: Steven Price <steven.price@arm.com>

Thanks,
Steve

> ---
>  kernel/events/core.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 7a028474caef..20e97c1aa4d6 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -13954,21 +13954,19 @@ static void perf_event_setup_cpumask(unsigned int cpu)
>  	struct cpumask *pmu_cpumask;
>  	unsigned int scope;
>  
> -	cpumask_set_cpu(cpu, perf_online_mask);
> -
>  	/*
>  	 * Early boot stage, the cpumask hasn't been set yet.
>  	 * The perf_online_<domain>_masks includes the first CPU of each domain.
> -	 * Always uncondifionally set the boot CPU for the perf_online_<domain>_masks.
> +	 * Always unconditionally set the boot CPU for the perf_online_<domain>_masks.
>  	 */
> -	if (!topology_sibling_cpumask(cpu)) {
> +	if (cpumask_empty(perf_online_mask)) {
>  		for (scope = PERF_PMU_SCOPE_NONE + 1; scope < PERF_PMU_MAX_SCOPE; scope++) {
>  			pmu_cpumask = perf_scope_cpumask(scope);
>  			if (WARN_ON_ONCE(!pmu_cpumask))
>  				continue;
>  			cpumask_set_cpu(cpu, pmu_cpumask);
>  		}
> -		return;
> +		goto end;
>  	}
>  
>  	for (scope = PERF_PMU_SCOPE_NONE + 1; scope < PERF_PMU_MAX_SCOPE; scope++) {
> @@ -13983,6 +13981,8 @@ static void perf_event_setup_cpumask(unsigned int cpu)
>  		    cpumask_any_and(pmu_cpumask, cpumask) >= nr_cpu_ids)
>  			cpumask_set_cpu(cpu, pmu_cpumask);
>  	}
> +end:
> +	cpumask_set_cpu(cpu, perf_online_mask);
>  }
>  
>  int perf_event_init_cpu(unsigned int cpu)


      reply	other threads:[~2024-09-12 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 14:50 [PATCH] perf: Fix topology_sibling_cpumask check warning on ARM kan.liang
2024-09-12 15:53 ` Steven Price [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=0a1f237f-281f-4a08-968f-6c6f94f0a035@arm.com \
    --to=steven.price@arm.com \
    --cc=hpa@zytor.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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