[PATCH 00/11] section name cleanup for x86

From: Tim Abbott
Date: Thu Apr 30 2009 - 20:14:32 EST


This patch series cleans up the section names on the x86
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 */

These patches are on top of the x86/kbuild branch of linux-tip.

-Tim Abbott


Anders Kaseorg (1):
x86: fix fragile computation of vsyscall address

Tim Abbott (10):
x86: Use macros for .bss.page_aligned section.
x86: Use section .data.page_aligned for the idt_table.
x86: Use macros for .data.page_aligned.
x86: convert compressed loader to use __HEAD and HEAD_TEXT macros.
x86: convert to use __HEAD and HEAD_TEXT macros.
x86: use NOSAVE_DATA macro for .data.nosave section.
x86: use new macro for .data.cacheline_aligned section.
x86: use new macros for .data.init_task.
x86: use new macro for .data.read_mostly section.
x86: convert to new generic read_mostly support.

arch/x86/Kconfig | 3 +
arch/x86/boot/compressed/head_32.S | 3 +-
arch/x86/boot/compressed/head_64.S | 3 +-
arch/x86/boot/compressed/vmlinux.lds.S | 6 +-
arch/x86/include/asm/cache.h | 2 -
arch/x86/kernel/head_32.S | 6 +-
arch/x86/kernel/head_64.S | 4 +-
arch/x86/kernel/init_task.c | 3 +-
arch/x86/kernel/traps.c | 6 +-
arch/x86/kernel/vmlinux.lds.S | 119 ++++++++------------------------
10 files changed, 49 insertions(+), 106 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/