Messages in this thread | | | Date | Tue, 6 Jun 2006 09:26:29 +0200 | From | Ingo Molnar <> | Subject | Re: 2.6.17-rc5-mm1 |
| |
* Barry K. Nathan <barryn@pobox.com> wrote:
> On 6/5/06, Andrew Morton <akpm@osdl.org> wrote: > >I guess we should force 8k stacks if the lockdep features are enabled. > > Also, Laurent is running "2.6.17-rc5-mm3-lockdep" (per his previous > message), i.e., 2.6.17-rc5-mm3 with Ingo's lockdep-combo patch added. > If you're wondering how I conclude the latter from the former, look at > this hunk from the lockdep-combo patch: > > --- linux.orig/Makefile > +++ linux/Makefile > @@ -1,7 +1,7 @@ > VERSION = 2 > PATCHLEVEL = 6 > SUBLEVEL = 17 > -EXTRAVERSION =-rc5-mm3 > +EXTRAVERSION =-rc5-mm3-lockdep > NAME=Lordi Rules > > And from the same patch: > > --- linux.orig/arch/i386/Makefile > +++ linux/arch/i386/Makefile > @@ -38,6 +38,10 @@ CFLAGS += $(call cc-option,-mpreferred-s > include $(srctree)/arch/i386/Makefile.cpu > > cflags-$(CONFIG_REGPARM) += -mregparm=3 > +# > +# Prevent tail-call optimizations, to get clearer backtraces: > +# > +cflags-$(CONFIG_FRAME_POINTER) += -fno-optimize-sibling-calls > > # temporary until string.h is fixed > cflags-y += -ffreestanding > > I would expect that to increase stack usage...
yes, and -pg (the one that creates the mcount callbacks that drive the lockdep tracer) increases the stack footprint too. But these items are only in my combo patch and in the lockdep tracer, not in -mm.
Ingo - 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/
| |