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 haveblue@us.ibm.com- 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/
This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:32 EST