From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id pBB00eT5017276 for ; Sat, 10 Dec 2011 18:00:40 -0600 Received: from one.firstfloor.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 502B72B302F for ; Sat, 10 Dec 2011 16:00:38 -0800 (PST) Received: from one.firstfloor.org (one.firstfloor.org [213.235.205.2]) by cuda.sgi.com with ESMTP id ZIZZ8DVijGVfSHaS for ; Sat, 10 Dec 2011 16:00:38 -0800 (PST) Date: Sun, 11 Dec 2011 01:00:36 +0100 From: Andi Kleen Subject: Re: XFS causing stack overflow Message-ID: <20111211000036.GH24062@one.firstfloor.org> References: <20111209115513.GA19994@infradead.org> <20111209221956.GE14273__25752.826271537$1323469420$gmane$org@dastard> <20111210221345.GG14273@dastard> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20111210221345.GG14273@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: Christoph Hellwig , linux-mm@kvack.org, "Ryan C. England" , Andi Kleen , xfs@oss.sgi.com > Where does the x86-64 do the interrupt stack switch? in entry_64.S > > I know the x86 32 bit interrupt handler switches to an irq/softirq > context stack, but the 64 bit one doesn't appear to. Indeed, > arch/x86/kernel/irq_{32,64}.c are very different, and only the 32 > bit irq handler switches to another stack to process the > interrupts... x86-64 always used interrupt stacks and has used softirq stacks for a long time. 32bit got to it much later (the only good thing left from that 4k stack "experiment") -Andi _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs