[v3] xen: fix CONFIG_DEBUG_LOCKS

[Xen-devel] [PATCH v3 0/2] xen: fix CONFIG_DEBUG_LOCKS

Juergen Gross posted 2 patches 4 years, 3 months ago

Diff against v2
Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/xen tags/patchew/20200121101301.421-1-jgross@suse.com

xen/Kconfig.debug         | 8 +++++++-
xen/common/spinlock.c     | 2 +-
xen/include/asm-arm/bug.h | 6 ++++--
xen/include/asm-x86/bug.h | 5 +++--
xen/include/xen/lib.h     | 4 ++++
5 files changed, 19 insertions(+), 6 deletions(-)

Expand all Fold all

[Xen-devel] [PATCH v3 0/2] xen: fix CONFIG_DEBUG_LOCKS

Posted by Juergen Gross 4 years, 3 months ago

CONFIG_DEBUG_LOCKS is using ASSERT() for catching issues making it
depend on CONFIG_DEBUG.

This series fixes that by using BUG_ON() instead. In order not to lose
the rather nice debugging information which condition was hit add a
config option to include a message similar to the one ASSERT() is
printing in case of BUG_ON() triggering.

Juergen Gross (2):
  xen: add config option to include failing condition in BUG_ON()
    message
  xen: make CONFIG_DEBUG_LOCKS usable without CONFIG_DEBUG

 xen/Kconfig.debug         | 8 +++++++-
 xen/common/spinlock.c     | 2 +-
 xen/include/asm-arm/bug.h | 6 ++++--
 xen/include/asm-x86/bug.h | 5 +++--
 xen/include/xen/lib.h     | 4 ++++
 5 files changed, 19 insertions(+), 6 deletions(-)

-- 
2.16.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel