> The most straight forward is to have a mechanism which forces everything > into the slow path in case of debugging, lack of progress, etc. The slow That's the abort address, right? For the generic case the fall back path would require disabling preemption unfortunately, for which we don't have a mechanism in user space. I think that is what Mathieu tried to implement here with this call. There may be some special cases where it's possible without preemption control, e.g. a malloc could just not use the per cpu cache. But I doubt that is possible in all cases that Mathieu envisions. But again would be a different code path, and I question the need for it when we can just let the operator of the debugger deal with it. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
