[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250819130802.GI3245006@noisy.programming.kicks-ass.net>
Date: Tue, 19 Aug 2025 15:08:02 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Menglong Dong <menglong8.dong@...il.com>, mingo@...hat.com,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, ast@...nel.org,
daniel@...earbox.net, john.fastabend@...il.com, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, simona.vetter@...ll.ch,
tzimmermann@...e.de, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH v2 2/3] sched: make migrate_enable/migrate_disable inline
On Tue, Aug 19, 2025 at 03:49:54PM +0300, Jani Nikula wrote:
> On Tue, 19 Aug 2025, Peter Zijlstra <peterz@...radead.org> wrote:
> >> +EXPORT_SYMBOL_GPL(runqueues);
> >
> > Oh no, absolutely not.
> >
> > You never, ever, export a variable, and certainly not this one.
>
> Tangential thought:
>
> I think it would be possible to warn about non-function exports at build
> time, and maybe plug it in W=1 builds.
>
Too much noise, there's a metric ton of variables exported. Sometimes
its unavoidable.
I just try and avoid wherever possible.
Powered by blists - more mailing lists