From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756393AbYDTOkn (ORCPT ); Sun, 20 Apr 2008 10:40:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751650AbYDTOkd (ORCPT ); Sun, 20 Apr 2008 10:40:33 -0400 Received: from sandeen.net ([209.173.210.139]:16158 "EHLO sandeen.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751268AbYDTOkc (ORCPT ); Sun, 20 Apr 2008 10:40:32 -0400 Message-ID: <480B55DF.90502@sandeen.net> Date: Sun, 20 Apr 2008 09:40:31 -0500 From: Eric Sandeen User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Willy Tarreau CC: Mark Lord , Andi Kleen , Adrian Bunk , Alan Cox , Shawn Bohrer , Ingo Molnar , Andrew Morton , Linux Kernel Mailing List , Arjan van de Ven , Thomas Gleixner Subject: Re: x86: 4kstacks default References: <20080419145948.GA4528@lintop> <20080420080901.GF1595@cs181133002.pp.htv.fi> <20080420090623.7b173ef1@the-village.bc.nu> <20080420085104.GG1595@cs181133002.pp.htv.fi> <20080420103611.2c0d3519@the-village.bc.nu> <20080420104444.GI1595@cs181133002.pp.htv.fi> <87y778aezh.fsf@basil.nowhere.org> <20080420124717.GH8474@1wt.eu> <480B44C4.4060104@rtr.ca> <480B4EA1.5070305@sandeen.net> <20080420142056.GC26536@1wt.eu> In-Reply-To: <20080420142056.GC26536@1wt.eu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Willy Tarreau wrote: > On Sun, Apr 20, 2008 at 09:09:37AM -0500, Eric Sandeen wrote: >> Mark Lord wrote: >>> Willy Tarreau wrote: >>>> What would really help would be to have 8k stacks with the lower page >>>> causing a fault and print a stack trace upon first access. That way, >>>> the safe setting would still report us useful information without >>>> putting users into trouble. >>> .. >>> >>> That's the best suggestion from this thread, by far! >>> Can you produce a patch for 2.6.26 for this? >>> Or perhaps someone else here, with the right code familiarity, could? >>> >>> Some sort of CONFIG option would likely be wanted to >>> either enable/disable this feature, of course. >> Changing the default warning threshold is easy, it's just a #define. > > I thought it was checked only at a few places (eg: during irqs). If so, > maybe it can miss some call chains ? Ah, ok I skimmed your first suggestion too quickly. 100% coverage reports on the initial access to the 2nd 4k that way would be nice. Well, it would be nice if we all really wanted 4k stacks some day... :) -Eric