From: Sam Ravnborg <sam@ravnborg.org>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] x86: clean up vdso-layout.lds.S
Date: Fri, 5 Jun 2009 22:07:01 +0200 [thread overview]
Message-ID: <20090605200701.GB23195@uranus.ravnborg.org> (raw)
In-Reply-To: <1244215559.1604.12.camel@nathan.suse.cz>
> > diff --git a/arch/x86/vdso/Makefile b/arch/x86/vdso/Makefile
> > index 16a9020..8c7f06a 100644
> > --- a/arch/x86/vdso/Makefile
> > +++ b/arch/x86/vdso/Makefile
> > @@ -23,7 +23,8 @@ $(obj)/vdso.o: $(obj)/vdso.so
> >
> > targets += vdso.so vdso.so.dbg vdso.lds $(vobjs-y)
> >
> > -export CPPFLAGS_vdso.lds += -P -C
> > +vdso-cppflags = -P -C
> > +export CPPFLAGS_vdso.lds += -m64 $(vdso-cppflags)
I am wondering why we need -P -C here - but we do not need it for lds.S files?
Seems like something we could let go.
> >
> > VDSO_LDFLAGS_vdso.lds = -m elf_x86_64 -Wl,-soname=linux-vdso.so.1 \
> > -Wl,-z,max-page-size=4096 -Wl,-z,common-page-size=4096
> > @@ -68,7 +69,7 @@ vdso32.so-$(VDSO32-y) += sysenter
> >
> > vdso32-images = $(vdso32.so-y:%=vdso32-%.so)
> >
> > -CPPFLAGS_vdso32.lds = $(CPPFLAGS_vdso.lds)
> > +CPPFLAGS_vdso32.lds = -m32 $(vdso-cppflags)
> > VDSO_LDFLAGS_vdso32.lds = -m elf_i386 -Wl,-soname=linux-gate.so.1
> >
> > # This makes sure the $(obj) subdirectory exists even though vdso32/
> > diff --git a/arch/x86/vdso/vdso-layout.lds.S b/arch/x86/vdso/vdso-layout.lds.S
> > index 634a2cf..1f4b215 100644
> > --- a/arch/x86/vdso/vdso-layout.lds.S
> > +++ b/arch/x86/vdso/vdso-layout.lds.S
> > @@ -22,16 +22,15 @@ SECTIONS
> > .eh_frame : { KEEP (*(.eh_frame)) } :text
> >
> > .dynamic : { *(.dynamic) } :text :dynamic
> > + .got : { *(.got.plt) *(.got) } :text
The style we try to introduce for .lds files in
arch/$ARCH/kernel/vmlinux.lds.S is much more C-like.
The above would have been:
.got : {
*(.got.plt)
*(.got)
} :text
Please use this all over so we have a consistent style in linker scripts.
> > .data : {
> > - *(.data*)
> > - *(.sdata*)
> > - *(.got.plt) *(.got)
> > - *(.gnu.linkonce.d.*)
> > - *(.bss*)
> > - *(.dynbss*)
> > - *(.gnu.linkonce.b.*)
> > + *(.data .data.* .gnu.linkonce.d.*)
> > + *(.bss .bss.* .gnu.linkonce.b.*)
> > + *(COMMON)
> > }
Where did *(.sdata*) go?
Why do we need *(.data .data.*) rather than *(.data*)?
*(.dynbss*)?
In your changelog you say:
"discard sections which are not useful to user-space" - but as you do not
list which one it is hard to tell what you removed on purpose
and what you removed by accident.
> >
> > .altinstructions : { *(.altinstructions) }
> > @@ -43,9 +42,49 @@ SECTIONS
> > */
> > . = ALIGN(0x100);
What is 0x100?
> >
> > - .text : { *(.text*) } :text =0x90909090
> > + .text : {
> > + *(.text .text.* .gnu.linkonce.t.*)
> > + } :text =0x90909090
> > +
> > + /* We would need a more sophisticated dynamic linker for the
> > + * vDSO to make the following sections work. Put them into
> > + * a special section and raise a link-time error if they get
> > + * used.
> > + */
> > + .broken : {
> > + /* Code in the Procedure Linkage Table will segfault */
> > + *(.plt)
> > +
> > + /* Relocation will not be done, so any pointers will
> > + * still point to the prelinked address, which is wrong
> > + */
> > + *(.data.rel.ro*)
> > + *(.gnu.linkonce.d.rel.ro.*)
> > +
> > + /* Initialization/termination won't work this way */
> > + *(.init) *(.fini)
> > + *(.preinit_array) *(.init_array*)
> > + *(.fini_array*)
> > +
> > + /* Thread-local data cannot be defined like this */
> > + *(.tdata .tdata.* .gnu.linkonce.td.*)
> > + *(.tbss .tbss.* .gnu.linkonce.tb.*)
> > + *(.tcommon)
> > + }
> > +
> > + /* These sections are not useful */
> > + /DISCARD/ : {
> > + *(.gnu.warning.*)
> > + *(.note.GNU-stack)
> > + }
> > }
> >
> > +ASSERT(!SIZEOF(.broken), "VDSO contains sections that don't work properly");
Can you give any better hints where to look and what to look for?
> > +
> > +/* Check that GOT has only the three entries defined by the ABI */
> > +ASSERT(SIZEOF(.got) == 3*__SIZEOF_POINTER__,
> > + "Found extra GOT entries. Check your use of external vars.");
Can you give any better hints where to look and what to look for?
Sam
next prev parent reply other threads:[~2009-06-05 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 14:05 Petr Tesarik
2009-06-05 15:25 ` Petr Tesarik
2009-06-05 16:27 ` Andi Kleen
2009-06-05 16:24 ` H. Peter Anvin
2009-06-09 7:32 ` Petr Tesarik
2009-06-05 20:07 ` Sam Ravnborg [this message]
2009-06-09 7:26 ` Petr Tesarik
2009-06-09 7:52 ` Roland McGrath
2009-06-09 7:57 ` Petr Tesarik
2009-06-09 8:09 ` Roland McGrath
2009-06-09 8:29 ` Petr Tesarik
2009-06-09 15:41 ` H. Peter Anvin
2009-06-09 18:11 ` Sam Ravnborg
2009-06-09 18:16 ` H. Peter Anvin
2009-06-09 19:22 ` Sam Ravnborg
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=20090605200701.GB23195@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ptesarik@suse.cz \
--cc=tglx@linutronix.de \
/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®