lkml.org 
[lkml]   [2006]   [Sep]   [28]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateThu, 28 Sep 2006 00:26:10 -0700
FromAndrew Morton <>
SubjectRe: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
On 28 Sep 2006 09:17:31 +0200
Andi Kleen <ak@muc.de> wrote:

> > Plan #17 is to just put the BUG inline and then put the EIP+file*+line into
> > a separate section, then search that section at BUG time to find the record
> > whose EIP points back at this ud2a.
> > 
> > It's a bit messy for modules, but it minimises the .text impact and keeps
> > disassembly happy, no?
> > 
> > And if done right it can probably be used by other architectures.
> 
> 
> The way x86-64 solved it was to turn the inline code into valid
> instructions. This can be done with two additional bytes.
> IMHO that's the right solution for the problem on i386 too
> 

That uses even more text.
-
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/

\
 
 \ /
  Last update: 2006-09-28 09:29    [from the cache]
©2003-2008