From: Christoph Hellwig <hch@lst.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC][WIP][PATCH] Add IRQSTACKS to ppc32
Date: Fri, 25 Apr 2008 09:23:32 +0200 [thread overview]
Message-ID: <20080425072332.GB23053@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0804240034160.23185@blarg.am.freescale.net>
On Thu, Apr 24, 2008 at 12:37:50AM -0500, Kumar Gala wrote:
> config IRQSTACKS
> bool "Use separate kernel stacks when processing interrupts"
> - depends on PPC64
Why do we have this as a user-selectable option? It should be on by
default on 32 or 64bit.
next prev parent reply other threads:[~2008-04-25 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 5:37 [RFC][WIP][PATCH] Add IRQSTACKS to ppc32 Kumar Gala
2008-04-24 7:18 ` Benjamin Herrenschmidt
2008-04-24 12:59 ` Kumar Gala
2008-04-24 14:53 ` Benjamin Herrenschmidt
2008-04-24 16:25 ` Kumar Gala
2008-04-25 7:23 ` Christoph Hellwig [this message]
2008-04-25 13:03 ` Benjamin Herrenschmidt
2008-04-25 13:37 ` Kumar Gala
2008-04-25 22:56 ` Paul Mackerras
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=20080425072332.GB23053@lst.de \
--to=hch@lst.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).