From: Arnd Bergmann <arnd@arndb.de>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH 00/19] unify init_task
Date: Thu, 11 Dec 2008 17:10:54 +0100 [thread overview]
Message-ID: <200812111710.55215.arnd@arndb.de> (raw)
In-Reply-To: <cover.1228966585.git.kyle@mcmartin.ca>
On Thursday 11 December 2008, Kyle McMartin wrote:
> Create a common kernel/init_task.c, and convert low hanging fruit to
> use it. Architecture maintainers will need to ensure that I didn't
> break anything before applying the init_task removal patch to their
> arch.
>
> A few architectures appear to possibly rely on link-ordering (with
> an extra-y makefile rule) and may need additional linker script rules.
FWIW, here is the alignment of init_thread_info on all architectures:
alpha: 2 * PAGE_SIZE
arm, avr32, frv, mn10300, s390, sh, x86: THREAD_SIZE
blackfin: THREAD_SIZE, but uses a different section
cris, m68k-sun3: PAGE_SIZE
h8300, m32r, m68knommu, ppc32, xtensa, m68k-std: 0x2000/8192
ia64: PAGE_SIZE (but ia64 is different)
mips: _PAGE_SIZE
parisc, ppc64: 16384
ppc32: 8192
um: KERNEL_STACK_SIZE
sparc: PAGE_SIZE with .text section
sparc64: 16384 (implicit)
This is the same as THREAD_SIZE on all architectures, except for
mips in certain configurations, which should be fixed.
Maybe we can get all of them to just use THREAD_SIZE in there?
Arnd <><
prev parent reply other threads:[~2008-12-11 16:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 3:52 [RFC PATCH 00/19] unify init_task Kyle McMartin
2008-12-11 3:52 ` [PATCH 01/19] add HAVE_ARCH_INIT_TASK Kyle McMartin
2008-12-11 3:52 ` [PATCH 02/19] add generic kernel/init_task.c Kyle McMartin
2008-12-11 3:52 ` [PATCH 03/19] x86: convert to generic init_task.c Kyle McMartin
2008-12-11 3:52 ` [PATCH 04/19] alpha: rename .data.init_thread to .data.init_task Kyle McMartin
2008-12-11 3:52 ` [PATCH 05/19] alpha: convert to generic init_task.c Kyle McMartin
2008-12-11 3:52 ` [PATCH 06/19] arm: " Kyle McMartin
2008-12-12 19:29 ` Russell King
2008-12-11 3:52 ` [PATCH 07/19] avr32: " Kyle McMartin
2009-01-06 12:55 ` Haavard Skinnemoen
2009-01-06 12:55 ` Haavard Skinnemoen
2008-12-11 3:52 ` [PATCH 08/19] blackfin: " Kyle McMartin
2008-12-11 12:55 ` Arnd Bergmann
2008-12-11 3:52 ` [PATCH 09/19] frv: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 10/19] h8300: " Kyle McMartin
2008-12-11 12:59 ` Arnd Bergmann
2008-12-11 3:52 ` [PATCH 11/19] m32r: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 12/19] m68knommu: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 13/19] mips: " Kyle McMartin
2008-12-11 13:04 ` Arnd Bergmann
2008-12-11 13:21 ` Ralf Baechle
2008-12-11 3:52 ` [PATCH 14/19] mn10300: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 15/19] parisc: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 16/19] powerpc: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 17/19] s390: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 18/19] sh: " Kyle McMartin
2008-12-11 3:52 ` [PATCH 19/19] xtensa: " Kyle McMartin
2008-12-11 8:57 ` [RFC PATCH 00/19] unify init_task Geert Uytterhoeven
2008-12-11 13:21 ` Arnd Bergmann
2008-12-11 14:02 ` Geert Uytterhoeven
2008-12-11 14:26 ` Arnd Bergmann
2008-12-11 12:56 ` Sam Ravnborg
2008-12-11 13:10 ` Arnd Bergmann
2008-12-11 13:23 ` Arnd Bergmann
2008-12-11 13:26 ` [PATCH] cris: convert to generic init_task Arnd Bergmann
2008-12-11 16:10 ` Arnd Bergmann [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=200812111710.55215.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.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