From: Tim Abbott <tabbott@MIT.EDU>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Anders Kaseorg <andersk@mit.edu>, Waseem Daher <wdaher@mit.edu>,
Denys Vlasenko <vda.linux@googlemail.com>,
Jeff Arnold <jbarnold@mit.edu>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
linux-m68k@vger.kernel.org, Tim Abbott <tabbott@mit.edu>
Subject: [PATCH 2/2] m68k: use new macros for .data.init_task.
Date: Thu, 30 Apr 2009 19:49:23 -0400 [thread overview]
Message-ID: <1241135363-8506-3-git-send-email-tabbott@mit.edu> (raw)
In-Reply-To: <1241135363-8506-2-git-send-email-tabbott@mit.edu>
.data.init_task should not need a separate output section; this change
moves it into the .data section.
I changed the aligment in both linker scripts to be THREAD_SIZE from
8192 and PAGE_SIZE, respectively. I'd like an ack from one of the
m68k maintainers that this is right.
Signed-off-by: Tim Abbott <tabbott@mit.edu>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
---
arch/m68k/kernel/process.c | 4 ++--
arch/m68k/kernel/vmlinux-std.lds | 3 +--
arch/m68k/kernel/vmlinux-sun3.lds | 2 +-
3 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/arch/m68k/kernel/process.c b/arch/m68k/kernel/process.c
index ec37fb5..6bf2cac 100644
--- a/arch/m68k/kernel/process.c
+++ b/arch/m68k/kernel/process.c
@@ -46,8 +46,8 @@ struct mm_struct init_mm = INIT_MM(init_mm);
EXPORT_SYMBOL(init_mm);
-union thread_union init_thread_union
-__attribute__((section(".data.init_task"), aligned(THREAD_SIZE)))
+union thread_union init_thread_union __init_task_data
+__attribute__((aligned(THREAD_SIZE)))
= { INIT_THREAD_INFO(init_task) };
/* initial task structure */
diff --git a/arch/m68k/kernel/vmlinux-std.lds b/arch/m68k/kernel/vmlinux-std.lds
index ac800bc..9e3cd1d 100644
--- a/arch/m68k/kernel/vmlinux-std.lds
+++ b/arch/m68k/kernel/vmlinux-std.lds
@@ -30,6 +30,7 @@ SECTIONS
RODATA
.data : { /* Data */
+ INIT_TASK_DATA(THREAD_SIZE)
CACHELINE_ALIGNED_DATA(16)
DATA_DATA
CONSTRUCTORS
@@ -76,8 +77,6 @@ SECTIONS
. = ALIGN(8192);
__init_end = .;
- .data.init_task : { *(.data.init_task) } /* The initial task and kernel stack */
-
_end = . ;
/* Sections to be discarded */
diff --git a/arch/m68k/kernel/vmlinux-sun3.lds b/arch/m68k/kernel/vmlinux-sun3.lds
index c192f77..8a988db 100644
--- a/arch/m68k/kernel/vmlinux-sun3.lds
+++ b/arch/m68k/kernel/vmlinux-sun3.lds
@@ -24,6 +24,7 @@ SECTIONS
_etext = .; /* End of text section */
.data : { /* Data */
+ INIT_TASK_DATA(THREAD_SIZE)
DATA_DATA
CONSTRUCTORS
. = ALIGN(16); /* Exception table */
@@ -70,7 +71,6 @@ __init_begin = .;
#endif
. = ALIGN(PAGE_SIZE);
__init_end = .;
- .data.init.task : { *(.data.init_task) }
.bss : { *(.bss) } /* BSS */
--
1.6.2.1
prev parent reply other threads:[~2009-04-30 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 23:49 [PATCH 0/2] section name cleanup for m68k Tim Abbott
2009-04-30 23:49 ` [PATCH 1/2] m68k: use new macro for .data.cacheline_aligned section Tim Abbott
2009-04-30 23:49 ` Tim Abbott [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=1241135363-8506-3-git-send-email-tabbott@mit.edu \
--to=tabbott@mit.edu \
--cc=andersk@mit.edu \
--cc=geert@linux-m68k.org \
--cc=jbarnold@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vda.linux@googlemail.com \
--cc=wdaher@mit.edu \
--cc=zippel@linux-m68k.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