mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, anand.gore@broadcom.com,
	william.zhang@broadcom.com, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Anna-Maria Gleixner <anna-maria@linutronix.de>,
	Sebastian Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"open list:PERFORMANCE EVENTS SUBSYSTEM" 
	<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf: Fix perf_event_{init,exit}_cpu stubs
Date: Fri, 4 Nov 2022 14:06:10 +0100	[thread overview]
Message-ID: <Y2UOQpniaV12E0P9@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20221103224303.3910486-1-f.fainelli@gmail.com>

On Thu, Nov 03, 2022 at 03:43:03PM -0700, Florian Fainelli wrote:
> The original commit that introduced those stubs was already at fault,
> but in the absence of a caller of perf_event_{init,exit}_cpu outside of
> code that is compiled regardless of CONFIG_PERF_EVENTS, the build
> failure cannot be observed. This was observed with the Android kernel to
> produce a build failure similar to this:
> 
>     In file included from ./include/uapi/linux/posix_types.h:5,
>                      from ./include/uapi/linux/types.h:14,
>                      from ./include/linux/types.h:6,
>                      from ./include/linux/limits.h:6,
>                      from ./include/linux/kernel.h:7,
>                      from ./include/linux/sched/mm.h:5,
>                      from kernel/cpu.c:6:
>     kernel/cpu.c: In function 'random_and_perf_prepare_fusion':
>     ./include/linux/stddef.h:8:14: error: called object is not a function or function pointer
>      #define NULL ((void *)0)
>                   ^
>     ./include/linux/perf_event.h:1607:29: note: in expansion of macro 'NULL'
>      #define perf_event_init_cpu NULL
>                                  ^~~~
>     kernel/cpu.c:1686:2: note: in expansion of macro 'perf_event_init_cpu'
>       perf_event_init_cpu(cpu);
>       ^~~~~~~~~~~~~~~~~~~

What is the actual problem reported here? Did you see all the other NULL
assignments in cpuhp_hp_states ?

> 
> Fixes: 00e16c3d68fc ("perf/core: Convert to hotplug state machine")
> Reported-by: Anand Gore <anand.gore@broadcom.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  include/linux/perf_event.h | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> index 0031f7b4d9ab..592040e2398c 100644
> --- a/include/linux/perf_event.h
> +++ b/include/linux/perf_event.h
> @@ -1678,8 +1678,15 @@ static struct device_attribute format_attr_##_name = __ATTR_RO(_name)
>  int perf_event_init_cpu(unsigned int cpu);
>  int perf_event_exit_cpu(unsigned int cpu);
>  #else
> -#define perf_event_init_cpu	NULL
> -#define perf_event_exit_cpu	NULL
> +static inline int perf_event_init_cpu(unsigned int cpu)
> +{
> +	return 0;
> +}
> +
> +static inline int perf_event_exit_cpu(unsigned int cpu)
> +{
> +	return 0;
> +}
>  #endif
>  
>  extern void __weak arch_perf_update_userpage(struct perf_event *event,
> -- 
> 2.25.1
> 

  reply	other threads:[~2022-11-04 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 22:43 Florian Fainelli
2022-11-04 13:06 ` Peter Zijlstra [this message]
2022-11-04 17:38   ` Florian Fainelli
2022-11-10 19:05     ` Florian Fainelli

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=Y2UOQpniaV12E0P9@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anand.gore@broadcom.com \
    --cc=anna-maria@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=f.fainelli@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=william.zhang@broadcom.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®