> 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.
It's not. It was always intended as one stack. It still is, for anyone not nesting debuggers (which afaik doesn't happen in-tree, it was only for Jan Beulich's magic debugger) I wrote the original code, so I should know. -Andi -- [email protected] -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
