From: David Daney <ddaney.cavm@gmail.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Cc: David Daney <david.daney@cavium.com>
Subject: [PATCH 1/2] vmlinux.lds.h: Allow architectures to add sections to the front of .bss
Date: Tue, 14 Aug 2012 11:08:00 -0700 [thread overview]
Message-ID: <1344967681-13179-2-git-send-email-ddaney.cavm@gmail.com> (raw)
In-Reply-To: <1344967681-13179-1-git-send-email-ddaney.cavm@gmail.com>
From: David Daney <david.daney@cavium.com>
Follow-on MIPS patch will put an object here that needs 64K alignment
to minimize padding.
For those architectures that don't define BSS_FIRST_SECTIONS, there is
no change.
Signed-off-by: David Daney <david.daney@cavium.com>
---
include/asm-generic/vmlinux.lds.h | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
index 4e2e1cc..d1ea7ce 100644
--- a/include/asm-generic/vmlinux.lds.h
+++ b/include/asm-generic/vmlinux.lds.h
@@ -530,9 +530,18 @@
*(.scommon) \
}
+/*
+ * Allow archectures to redefine BSS_FIRST_SECTIONS to add extra
+ * sections to the front of bss.
+ */
+#ifndef BSS_FIRST_SECTIONS
+#define BSS_FIRST_SECTIONS
+#endif
+
#define BSS(bss_align) \
. = ALIGN(bss_align); \
.bss : AT(ADDR(.bss) - LOAD_OFFSET) { \
+ BSS_FIRST_SECTIONS \
*(.bss..page_aligned) \
*(.dynbss) \
*(.bss) \
--
1.7.2.3
next prev parent reply other threads:[~2012-08-14 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 18:07 [PATCH 0/2] Align MIPS swapper_pg_dir for faster code David Daney
2012-08-14 18:08 ` David Daney [this message]
2012-08-14 18:08 ` [PATCH 1/2] vmlinux.lds.h: Allow architectures to add sections to the front of .bss David Daney
2012-08-14 18:08 ` [PATCH 2/2] MIPS: Align swapper_pg_dir to 64K for better TLB Refill code David Daney
2012-08-14 18:08 ` David Daney
2012-08-14 18:39 ` [PATCH 0/2] Align MIPS swapper_pg_dir for faster code Arnd Bergmann
2012-08-15 10:57 ` Ralf Baechle
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=1344967681-13179-2-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=arnd@arndb.de \
--cc=david.daney@cavium.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).