Re: top stack (l)users for 2.5.69

[Dave Hansen]

Jonathan Lundell wrote:
> One thing that would help (aside from separate interrupt stacks) 
> would be a guard page below the stack. That wouldn't require any 
> physical memory to be reserved, and would provide positive indication 
> of stack overflow without significant runtime overhead.

x86 doesn't really have big physical shortages right now.  But, the
_virtual_ shortages are significant.  The guard page just increases the
virtual cost by 50%.

The stack overflow checking in -mjb uses gcc's mcount mechanism to
detect overflows.  It should get called on every single function call.

-- 
Dave Hansen
[e-mail]