From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] arch/sh: use __page_aligned_bss
Date: Wed, 28 May 2008 17:05:15 +0100 [thread overview]
Message-ID: <483D82BB.8040005@goop.org> (raw)
The patch "make page-aligned data and bss less fragile" introduces
__page_aligned_data and __page_aligned_bss to make sure that page
aligned things remain so, even if there are non-page-sized
page-aligned things.
This paragraph converts the two C instances of page-aligned bss
variables to use them. It's a purely decorative patch.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Cc: Paul Mundt <lethal@linux-sh.org>
---
arch/sh/kernel/irq.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
===================================================================
--- a/arch/sh/kernel/irq.c
+++ b/arch/sh/kernel/irq.c
@@ -9,6 +9,7 @@
#include <linux/irq.h>
#include <linux/interrupt.h>
#include <linux/module.h>
+#include <linux/linkage.h>
#include <linux/kernel_stat.h>
#include <linux/seq_file.h>
#include <asm/processor.h>
@@ -157,11 +158,8 @@
}
#ifdef CONFIG_IRQSTACKS
-static char softirq_stack[NR_CPUS * THREAD_SIZE]
- __attribute__((__section__(".bss.page_aligned")));
-
-static char hardirq_stack[NR_CPUS * THREAD_SIZE]
- __attribute__((__section__(".bss.page_aligned")));
+static char softirq_stack[NR_CPUS * THREAD_SIZE] __page_aligned_bss;
+static char hardirq_stack[NR_CPUS * THREAD_SIZE] __page_aligned_bss;
/*
* allocate per-cpu stacks for hardirq and for softirq processing
next reply other threads:[~2008-05-28 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 16:05 Jeremy Fitzhardinge [this message]
2008-05-29 4:17 ` [PATCH 3/3] arch/sh: use __page_aligned_bss Paul Mundt
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=483D82BB.8040005@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.