[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0905171552020.3301@localhost.localdomain>
Date: Sun, 17 May 2009 15:54:35 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Hugh Dickins <hugh@...itas.com>
cc: Andi Kleen <ak@...ux.intel.com>,
Ian Campbell <ian.campbell@...rix.com>,
Jakub Jelinek <jakub@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jesper Nilsson <jesper.nilsson@...s.com>,
Johannes Weiner <hannes@...xchg.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Fix print out of function which called WARN_ON()
On Sun, 17 May 2009, Hugh Dickins wrote:
>
> No, not sure at all, that was just a conclusion I jumped to.
> Though I think I was seeing it on x86-32 too.
Ok, the 32-bit calling convention doesn't do any of that, even though we
compile the kernel with -mregparm=3. Any function with varargs arguments
gets all arguments passed on the stack, and we just pass the frame pointer
along, so there's no extra buffers.
So if you saw it on x86-32, then I think the only empty hole is indeed
due to that 'char function[KSYM_SYMBOL_LEN]' (and whatever stack alignment
code gcc does). And yes, it should be much better now.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists