From: "Jürgen Groß" <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jan Beulich <jbeulich@suse.com>,
oe-kbuild-all@lists.linux.dev, xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.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)
Date: Thu, 27 Mar 2025 15:21:45 +0100 [thread overview]
Message-ID: <c18a543c-4df2-4744-bf16-e888a832d634@suse.com> (raw)
In-Reply-To: <20250327141316.GBZ-Vc_NybN1cIEePu@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 965 bytes --]
On 27.03.25 15:13, Borislav Petkov wrote:
> On Wed, Jul 24, 2024 at 11:55:39AM +0200, Jürgen Groß wrote:
>> I'd prefer a general way to handle this problem, like e.g. some kind of
>> __refdata tagging for percpu variables.
>
> Any reason for not doing the trivial thing?
>
> diff --git a/arch/x86/xen/multicalls.c b/arch/x86/xen/multicalls.c
> index 10c660fae8b3..100bfaba3f4d 100644
> --- a/arch/x86/xen/multicalls.c
> +++ b/arch/x86/xen/multicalls.c
> @@ -53,7 +53,7 @@ struct mc_debug_data {
> };
>
> static DEFINE_PER_CPU(struct mc_buffer, mc_buffer);
> -static struct mc_debug_data mc_debug_data_early __initdata;
> +static struct mc_debug_data mc_debug_data_early;
> static DEFINE_PER_CPU(struct mc_debug_data *, mc_debug_data) =
> &mc_debug_data_early;
> static struct mc_debug_data __percpu *mc_debug_data_ptr;
Well, that is wasting nearly 3kB of the data section.
Maybe not a big deal, but still...
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-03-27 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202407240907.u0NJHgTu-lkp@intel.com>
[not found] ` <a9b1e875-5bf8-4755-ad2e-78ab2eb02c97@suse.com>
[not found] ` <fc4b5a0c-19dc-4741-b184-08b704444a1b@suse.com>
[not found] ` <3a847f18-750f-4bd2-9cac-37c4b9bdc84b@suse.com>
2025-03-27 14:13 ` Borislav Petkov
2025-03-27 14:21 ` Jürgen Groß [this message]
2025-03-27 14:40 ` Borislav Petkov
2025-03-27 15:15 ` Jürgen Groß
2025-03-27 15:24 ` Borislav Petkov
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=c18a543c-4df2-4744-bf16-e888a832d634@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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®