From: Paul Mundt <lethal@linux-sh.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: should there still be arch-specific 4KSTACKS support?
Date: Mon, 25 Jun 2012 16:44:37 +0900 [thread overview]
Message-ID: <20120625074436.GC24033@linux-sh.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1206231142150.14887@oneiric>
On Sat, Jun 23, 2012 at 11:47:33AM -0400, Robert P. J. Day wrote:
>
> via some convoluted logic, i ended up doing the following search:
>
> $ grep -r 4KSTACKS *
> arch/sh/configs/r7785rp_defconfig:CONFIG_4KSTACKS=y
> arch/sh/Kconfig.debug:config 4KSTACKS
> arch/sh/include/asm/thread_info.h:#if defined(CONFIG_4KSTACKS)
> arch/mn10300/include/asm/thread_info.h:#ifdef CONFIG_4KSTACKS
> arch/m68k/Kconfig.machine:config 4KSTACKS
> arch/m68k/configs/m5208evb_defconfig:# CONFIG_4KSTACKS is not set
> arch/m68k/configs/m5275evb_defconfig:# CONFIG_4KSTACKS is not set
> arch/m68k/configs/m5475evb_defconfig:# CONFIG_4KSTACKS is not set
> arch/m68k/include/asm/thread_info.h:#ifdef CONFIG_4KSTACKS
> arch/c6x/include/asm/thread_info.h:#ifdef CONFIG_4KSTACKS
> drivers/lguest/interrupts_and_traps.c: * Depending on the CONFIG_4KSTACKS option, the Guest can have one or
> kernel/lockdep.c: * hardirq contexts (such as on 4KSTACKS), so only
> $
>
> so even though 4KSTACKS support was officially removed in June of
> 2010:
>
> $ git show dcfa7262
>
> there's still traces of it, some of it obviously harmless, leftover
> cruft, but it would appear that both sh and m68k still provide a
> 4KSTACKS config option.
>
> how much of that can be tossed as useless?
>
None. What x86 did with its implementation has no bearing on anyone else.
You can read the following for more information:
http://lists.linuxfoundation.org/pipermail/ltsi-dev/2012-May/000099.html
prev parent reply other threads:[~2012-06-25 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 15:47 should there still be arch-specific 4KSTACKS support? Robert P. J. Day
2012-06-23 18:51 ` Geert Uytterhoeven
2012-06-29 6:10 ` Greg Ungerer
2012-06-25 7:44 ` Paul Mundt [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=20120625074436.GC24033@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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.