[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH for-4.10] common/multicall: Increase debugability for bad hypercalls
On 10/31/2017 05:18 PM, Andrew Cooper wrote: > 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. > > Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |