mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Tesarik <ptesarik@suse.cz>
To: linux-kernel@vger.kernel.org, linux-x86_64@vger.kernel.org,
	mingo@elte.hu, andi@firstfloor.org
Cc: zwane@arm.linux.org.uk, roland@redhat.com,
	Petr Tesarik <ptesarik@suse.cz>
Subject: [PATCH 2/4] x86: Cleanup vdso-layout.lds.S
Date: Thu, 14 May 2009 15:06:40 +0200	[thread overview]
Message-ID: <2bc7564b5c902a0ebabd5ab652b12c1ffa4214eb.1242299014.git.ptesarik@suse.cz> (raw)
In-Reply-To: <f249c3f58a699ce72b6cb416ddff98811848ff6f.1242299014.git.ptesarik@suse.cz>
In-Reply-To: <cover.1242299014.git.ptesarik@suse.cz>

Make the following changes:
  - move linker-generated sections out of .data
  - add all (even theoretically) possible rodata, data and text input
    sections to their respective output sections
  - discard .altinstructions and .altinstr_replacements

Since the .altinstructions section is currently not used anyway, this
is a pure cleanup.

Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
---
 arch/x86/vdso/vdso-layout.lds.S |   25 ++++++++++++++++++-------
 1 files changed, 18 insertions(+), 7 deletions(-)

diff --git a/arch/x86/vdso/vdso-layout.lds.S b/arch/x86/vdso/vdso-layout.lds.S
index 634a2cf..aaa3026 100644
--- a/arch/x86/vdso/vdso-layout.lds.S
+++ b/arch/x86/vdso/vdso-layout.lds.S
@@ -21,29 +21,40 @@ SECTIONS
 	.eh_frame_hdr	: { *(.eh_frame_hdr) }		:text	:eh_frame_hdr
 	.eh_frame	: { KEEP (*(.eh_frame)) }	:text
 
+	/* Linker-generated sections */
 	.dynamic	: { *(.dynamic) }		:text	:dynamic
+	.got		: { *(.got) }			:text
+	.got.plt	: { *(.got.plt) }
+	.dynbss		: { *(.dynbss) }
 
-	.rodata		: { *(.rodata*) }		:text
+	.rodata		: {
+	      *(.rodata*)
+	      *(.gnu.linkonce.r.*)
+	}
 	.data		: {
 	      *(.data*)
 	      *(.sdata*)
-	      *(.got.plt) *(.got)
 	      *(.gnu.linkonce.d.*)
 	      *(.bss*)
-	      *(.dynbss*)
+	      *(.sbss*)
 	      *(.gnu.linkonce.b.*)
 	}
 
-	.altinstructions	: { *(.altinstructions) }
-	.altinstr_replacement	: { *(.altinstr_replacement) }
-
 	/*
 	 * Align the actual code well away from the non-instruction data.
 	 * This is the best thing for the I-cache.
 	 */
 	. = ALIGN(0x100);
 
-	.text		: { *(.text*) }			:text	=0x90909090
+	.text		: {
+	      *(.text*)
+	      *(.gnu.linkonce.t.*)
+	}						:text	=0x90909090
+
+	/DISCARD/ : {
+	      *(.altinstructions)
+	      *(.altinstr_replacement)
+	}
 }
 
 /*
-- 
1.6.0.2



  reply	other threads:[~2009-05-14 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 13:06 [PATCH 0/4] x86-64: fix vclock_gettime() Petr Tesarik
2009-05-14 12:58 ` Andi Kleen
2009-05-14 13:01   ` Petr Tesarik
2009-05-14 14:02     ` Andi Kleen
2009-05-14 14:27       ` Petr Tesarik
2009-05-14 13:06 ` [PATCH 1/4] x86: Use vdso*-syms.h instead of vdso*-syms.lds Petr Tesarik
2009-05-14 13:06   ` Petr Tesarik [this message]
2009-05-14 13:06     ` [PATCH 3/4] x86-64: link vDSO into the kernel with relocations Petr Tesarik
2009-05-14 13:07       ` [PATCH 4/4] x86: add rdtsc_barrier() to vgetns() Petr Tesarik
2009-05-14 13:17 ` [PATCH 0/4] x86-64: fix vclock_gettime() Petr Tesarik

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=2bc7564b5c902a0ebabd5ab652b12c1ffa4214eb.1242299014.git.ptesarik@suse.cz \
    --to=ptesarik@suse.cz \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=zwane@arm.linux.org.uk \
    /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®