[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250327152450.GBZ-VtwmD3altwx_rI@fat_crate.local>
Date: Thu, 27 Mar 2025 16:24:50 +0100
From: Borislav Petkov <bp@...en8.de>
To: Jürgen Groß <jgross@...e.com>
Cc: Jan Beulich <jbeulich@...e.com>, oe-kbuild-all@...ts.linux.dev,
xen-devel@...ts.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
kernel test robot <lkp@...el.com>, x86-ml <x86@...nel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [xen-tip:linux-next 12/12] WARNING: modpost: vmlinux: section
mismatch in reference: mc_debug_data+0x0 (section: .data) ->
mc_debug_data_early (section: .init.data)
On Thu, Mar 27, 2025 at 04:15:11PM +0100, Jürgen Groß wrote:
> Another approach could be to have:
>
> -static DEFINE_PER_CPU(struct mc_debug_data *, mc_debug_data) =
> - &mc_debug_data_early;
> +static DEFINE_PER_CPU(struct mc_debug_data *, mc_debug_data);
>
> and to use an inline access function returning &mc_debug_data_early
> if the percpu variable is NULL. This access function could be __ref.
>
> It is a debug feature after all, so having a few additional instructions
> isn't the end of the world.
Yap, makes sense to me too.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists