> I think all of this stems from unfortunate naming. DEBUG_STACK isn't > one stack -- it's a debug stack *array*. The IST shift mechanism > means that we can use different entries in that array as our stacks > depending on how deeply nested we are.
I still think it's a terrible idea. > > Just handling it in the code is simple enough. > > It seems to account for over half the asm diff. I'm talking about the > addition of approximately two lines of C and the removal of a huge > chunk of the asm diff. It's just adding offsets to the stack code. Nothing complicated. It's also straight forward code. Far more preferable than your magic overlapping stacks. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
