[xen master] common/multicall: Increase debugability for bad hypercalls
Author: Andrew Cooper <[hidden email]>
AuthorDate: Tue Oct 31 17:07:41 2017 +0000
Commit: Andrew Cooper <[hidden email]>
CommitDate: Thu Nov 2 16:49:57 2017 +0000
common/multicall: Increase debugability for bad hypercalls
While investigating an issue (in a new codepath I'd introduced, as it turns
out), leaving interrupts disabled manifested as a subsequent op in the
multicall failing a check_lock() test.
The codepath would have hit the ASSERT_NOT_IN_ATOMIC on the return-to-guest
path, had it not hit the check_lock() first.
Call ASSERT_NOT_IN_ATOMIC() after each operation in the multicall, to make
failures more obvious.
+ * In the unlikely event that a hypercall has left interrupts,
+ * spinlocks, or other things in a bad way, continuing the multicall
+ * will typically lead to far more subtle issues to debug.
generated by git-patchbot for /home/xen/git/xen.git#master