[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1241136247-10623-1-git-send-email-tabbott@mit.edu>
Date: Thu, 30 Apr 2009 20:04:02 -0400
From: Tim Abbott <tabbott@....EDU>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Linux kernel mailing list <linux-kernel@...r.kernel.org>,
Anders Kaseorg <andersk@....edu>,
Waseem Daher <wdaher@....edu>,
Denys Vlasenko <vda.linux@...glemail.com>,
Jeff Arnold <jbarnold@....edu>,
Tony Luck <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
Tim Abbott <tabbott@....edu>
Subject: [PATCH 0/5] section name cleanup for ia64
This patch series cleans up the section names on the ia64
architecture. It requires the architecture-independent macro
definitions from this patch series:
<http://www.spinics.net/lists/mips/msg33499.html>
The long-term goal here is to add support for building the kernel with
-ffunction-sections -fdata-sections. This requires renaming all the
magic section names in the kernel of the form .text.foo, .data.foo,
.bss.foo, and .rodata.foo to not have collisions with sections
generated for code like:
static int nosave = 0; /* -fdata-sections places in .data.nosave */
static void head(); /* -ffunction-sections places in .text.head */
Note that these patches have not been boot-tested (aside from testing
the analogous changes on x86), since I don't have access to the
appropriate hardware.
-Tim Abbott
Tim Abbott (5):
ia64: Use .ref.text, not .text.init for start_ap.
ia64: use new macro for .data.cacheline_aligned section.
ia64: use new macros for .data.init_task
ia64: use new macro for .data.read_mostly section.
ia64: convert to new generic read_mostly support.
arch/ia64/Kconfig | 3 +++
arch/ia64/include/asm/cache.h | 2 --
arch/ia64/kernel/head.S | 2 +-
arch/ia64/kernel/init_task.c | 2 +-
arch/ia64/kernel/vmlinux.lds.S | 15 +++------------
arch/ia64/xen/xensetup.S | 3 ++-
6 files changed, 10 insertions(+), 17 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists