From: "Alexander Stohr" <alexander.stohr@gmx.de>
To: <linux-kernel@vger.kernel.org>, <kai@germaschewski.name>,
"Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] fix for pseudo symbol swapping with scripts/kallsyms - linux-2.6.10-rc1-bk12 & gcc 3.4.2
Date: Sat, 6 Nov 2004 23:32:17 +0100 [thread overview]
Message-ID: <000c01c4c450$7faa1fe0$8511050a@alexs> (raw)
In-Reply-To: <20041106210548.GA18305@mars.opasia.dk>
i will try to give it a try on monday
when i am back to the console of that machine.
Thanks for your good hints. I assume that function
alignment might expose some other benefits as well.
-Alex.
----- Original Message -----
From: "Sam Ravnborg" <sam@mars.opasia.dk>
To: "Alexander Stohr" <Alexander.Stohr@gmx.de>; <linux-kernel@vger.kernel.org>; <kai@germaschewski.name>; <sam@ravnborg.org>
Sent: Saturday, November 06, 2004 10:05 PM
Subject: Re: [PATCH] fix for pseudo symbol swapping with scripts/kallsyms - linux-2.6.10-rc1-bk12 & gcc 3.4.2
> On Sat, Nov 06, 2004 at 12:25:58AM +0100, Sam Ravnborg wrote:
> > The linker will adhere to any alingment demands in the section,
> > but not the labels. So the real fix is to make sure the labels are
> > defined inside the section.
> > Please try attached (untested) patch.
> >
> > Check that error is present without patch, and it is fixed with the patch.
>
> This patch is better - we cannot define sections within sections.
>
> Sam
>
> ===== include/asm-generic/vmlinux.lds.h 1.16 vs edited =====
> --- 1.16/include/asm-generic/vmlinux.lds.h 2004-10-06 18:45:06 +02:00
> +++ edited/include/asm-generic/vmlinux.lds.h 2004-11-06 21:56:11 +01:00
> @@ -6,6 +6,11 @@
> #define VMLINUX_SYMBOL(_sym_) _sym_
> #endif
>
> +/* Aling functions to a 32 byte boundary.
> + * This prevents lables defined to mark start/end of section to differ
> + * during pass 1 and pass 2 when generating Systme.map */
> +#define ALIGN_FUNCTION() . = ALIGN(8)
> +
> #define RODATA \
> .rodata : AT(ADDR(.rodata) - LOAD_OFFSET) { \
> *(.rodata) *(.rodata.*) \
> @@ -77,11 +82,13 @@
> }
>
> #define SCHED_TEXT \
> + ALIGN_FUNCTION(); \
> VMLINUX_SYMBOL(__sched_text_start) = .; \
> *(.sched.text) \
> VMLINUX_SYMBOL(__sched_text_end) = .;
>
> #define LOCK_TEXT \
> + ALIGN_FUNCTION(); \
> VMLINUX_SYMBOL(__lock_text_start) = .; \
> *(.spinlock.text) \
> VMLINUX_SYMBOL(__lock_text_end) = .;
>
prev parent reply other threads:[~2004-11-06 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 14:33 Alexander Stohr
2004-11-05 23:25 ` Sam Ravnborg
2004-11-06 21:05 ` Sam Ravnborg
2004-11-06 22:32 ` Alexander Stohr [this message]
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='000c01c4c450$7faa1fe0$8511050a@alexs' \
--to=alexander.stohr@gmx.de \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®