From patchwork Thu Jan 9 13:48:23 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?b?SsO8cmdlbiBHcm/Dnw==?= X-Patchwork-Id: 11325713 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id DCED1139A for ; Thu, 9 Jan 2020 13:49:56 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C338E20661 for ; Thu, 9 Jan 2020 13:49:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C338E20661 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1ipYBN-0003Hz-S9; Thu, 09 Jan 2020 13:49:05 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1ipYBM-0003Hs-Kf for xen-devel@lists.xenproject.org; Thu, 09 Jan 2020 13:49:04 +0000 X-Inumbo-ID: cb113bf7-32e6-11ea-b9d3-12813bfff9fa Received: from mx2.suse.de (unknown [195.135.220.15]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id cb113bf7-32e6-11ea-b9d3-12813bfff9fa; Thu, 09 Jan 2020 13:49:02 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 55C4FAD76; Thu, 9 Jan 2020 13:48:28 +0000 (UTC) From: Juergen Gross To: xen-devel@lists.xenproject.org Date: Thu, 9 Jan 2020 14:48:23 +0100 Message-Id: <20200109134825.31482-1-jgross@suse.com> X-Mailer: git-send-email 2.16.4 Subject: [Xen-devel] [PATCH v2 0/2] xen: fix CONFIG_DEBUG_LOCKS X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Juergen Gross , Stefano Stabellini , Julien Grall , Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Andrew Cooper , Ian Jackson , Jan Beulich , =?utf-8?q?Roger_Pau_Monn=C3=A9?= MIME-Version: 1.0 Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" 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_OM() 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 | 6 ++++++ xen/common/spinlock.c | 2 +- xen/include/asm-x86/bug.h | 5 +++-- xen/include/xen/lib.h | 5 +++++ 4 files changed, 15 insertions(+), 3 deletions(-)