[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42cbca3dc56a1fde7d472754430458e2de8412a1@intel.com>
Date: Tue, 19 Aug 2025 15:49:54 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: Peter Zijlstra <peterz@...radead.org>, Menglong Dong
<menglong8.dong@...il.com>
Cc: 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, 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.
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists