From: Daniel Phillips <phillips@istop.com>
To: Mark Lord <lkml@rtr.ca>
Subject: Re: RFC: i386: kill !4KSTACKS
Date: Wed, 7 Sep 2005 01:48:18 -0400
User-Agent: KMail/1.8
Cc: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>, linux-kernel@vger.kernel.org,
       Andi Kleen <ak@suse.de>
References: <20050904145129.53730.qmail@web50202.mail.yahoo.com> <431E497A.4080303@rtr.ca> <200509070016.42121.phillips@istop.com>
In-Reply-To: <200509070016.42121.phillips@istop.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200509070148.18822.phillips@istop.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 857
Lines: 19

On Wednesday 07 September 2005 00:16, Daniel Phillips wrote:
> ...as long as ->task and ->previous_esp are initialized,
> staying on the bigger stack looks fine (previous_esp is apparently used
> only for backtrace) ... just like do_IRQ.

Ahem, but let me note before somebody else does: it isn't interrupt context, 
it is normal process context - while an interrupt can ignore most of the 
thread_info fields, a normal process has to worry about all 9.  To be on the 
safe side, the first 8 need to be copied into and out of the ndis stack, with 
preempt disabled until after the stack switch.

Regards,

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