Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761703AbYFTPrd (ORCPT ); Fri, 20 Jun 2008 11:47:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758277AbYFTPrY (ORCPT ); Fri, 20 Jun 2008 11:47:24 -0400 Received: from mx1.redhat.com ([66.187.233.31]:41084 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757385AbYFTPrX (ORCPT ); Fri, 20 Jun 2008 11:47:23 -0400 Date: Fri, 20 Jun 2008 11:47:12 -0400 (EDT) From: Mikulas Patocka To: David Miller cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org, agk@redhat.com Subject: Re: stack overflow on Sparc64 In-Reply-To: <20080617.210159.141238856.davem@davemloft.net> Message-ID: References: <20080617.210159.141238856.davem@davemloft.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1371 Lines: 44 > It could still be improved a lot, however. > >> Long-term consideration: Is it possible to implement interrupt stacks on >> sparc64? Functions on sparc eat stack much more aggressively than on other >> architectures (minimum stack size for a function is 192 bytes). > > I had a patch but at the time I wrote it (several years ago) I > couldn't make it stable enough to put mainline, I may resurrect it. > > I just did a quick scan and I can't find the last copy I had, and > things have changed enough that I'd probably work from scratch > anyways. > > But the level of recursion possible by the current device layer is > excessive and needs to be curtained irrespective of these generic > wakeup and sparc64 interrupt stack issues. I took another few traces (to track the whole stack content) and there is another problem: nested interrupts. Does Sparc64 limit them somehow? sys_call_table timer_interrupt irq_exit do_softirq __do_softirq run_timer_softirq _spin_unlock sys_call_table handler_irq handler_fasteoi_irq handle_irq_event ide_intr ide_dma_intr task_end_request ide_end_request __ide_end_request ... Mikulas -- 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/