[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <364b3128f40d44939586bdc8e8ae7c9d@AcuMS.aculab.com>
Date: Fri, 22 Dec 2023 09:48:50 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Masahiro Yamada' <masahiroy@...nel.org>, "deller@...nel.org"
<deller@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Arnd
Bergmann" <arnd@...db.de>, "linux-modules@...r.kernel.org"
<linux-modules@...r.kernel.org>, "linux-arch@...r.kernel.org"
<linux-arch@...r.kernel.org>, Luis Chamberlain <mcgrof@...nel.org>
Subject: RE: [PATCH 0/4] Section alignment issues?
...
> diff --git a/include/linux/init.h b/include/linux/init.h
> index 3fa3f6241350..650311e4b215 100644
> --- a/include/linux/init.h
> +++ b/include/linux/init.h
> @@ -264,6 +264,7 @@ extern struct module __this_module;
> #define ____define_initcall(fn, __stub, __name, __sec) \
> __define_initcall_stub(__stub, fn) \
> asm(".section \"" __sec "\", \"a\" \n" \
> + ".balign 4 \n" \
> __stringify(__name) ": \n" \
> ".long " __stringify(__stub) " - . \n" \
> ".previous \n"); \
>
>
>
> Then, "this section requires at least 4 byte alignment"
> is recorded in the sh_addralign field.
Perhaps one of the headers should contain (something like):
#ifdef CONFIG_64
#define BALIGN_PTR ".balign 8\n"
#else
#define BALIGN_PTR ".balign 4\n"
#endif
to make it all easier (although that example doesn't need it).
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists