Received: by 10.213.65.68 with SMTP id h4csp220402imn; Fri, 30 Mar 2018 04:19:28 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+anfu030JH1BxgJUiVzJeq02fefDelxWNw/XS+PxmnHVGKEprBCR7dYOLddzPDiav5XgRo X-Received: by 2002:a17:902:ab81:: with SMTP id f1-v6mr12338385plr.5.1522408768053; Fri, 30 Mar 2018 04:19:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522408768; cv=none; d=google.com; s=arc-20160816; b=XQ/wLIzlB7R/OVCCrVH9vDrT3f+M7TT7ltMWhfKGQTmNDqpDfJ/K0ZNZmsbnv/2HPl FDt8ZlackzJsAizi9q+F74KTABy/G8NQhjT7BNWpq/cZbnZsUwBzkevAlmb9PcsV2DUF H7T46aaiHjdAIZ91iWp+8kBM8wPtwcUv0Cpc2G0ud4j+4rIDKpEhLDDgFrAr7smvRzeF crgtTXp8Lw5SGt5pk1jqDX0gAxkkwFOe9aknTzF1o5FIV5UMw/ChetoSP3n+RQRRitm6 GBAGSc73ssG+zMkX392WVkQS51Si9026XAhqYdJOes1X01Occ+hPfLghGCK1XK4i06Ay 7lQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=s1+/v0bKB40agl7pRpciyCPIhtr1122Hrwf0L5dpSdQ=; b=ib3V+ZV38sapXVOK/6fCa6wsI6suUkCD/xnIZCLXTk8mHHbQWulZfzHBzAeBjnmRDD 92ZZpXiq6uV2H+N0wbqP1EToi0ZWS0tjxSaOI8xqRj2oA2yKrtJ0fK8kfb8hnH1HywM2 o9WLD54KAtwCSLahfCFekwOTWAmeGeiT7+3+Xem1BoIKWMwhlZpUyldlWc5rrQUNeHrd MpgteIicLvN1+CY0BVQEDkluKIDLaHBvJC1jZDzSDRL8SNsgSU02DwlJtRCTL4A0qEOW 7fS9OkFgh1pylfi4ldAQ2O/n5R7ixBlaxh8fc9s1cxTZIatfA2bsTjPgmlX/MPQQEFPX RVnw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=fRdoNz7o; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b11-v6si9038571plk.688.2018.03.30.04.19.12; Fri, 30 Mar 2018 04:19:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=fRdoNz7o; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751237AbeC3LSA (ORCPT + 99 others); Fri, 30 Mar 2018 07:18:00 -0400 Received: from mail-wr0-f195.google.com ([209.85.128.195]:33498 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751096AbeC3LR7 (ORCPT ); Fri, 30 Mar 2018 07:17:59 -0400 Received: by mail-wr0-f195.google.com with SMTP id z73so7796391wrb.0 for ; Fri, 30 Mar 2018 04:17:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=s1+/v0bKB40agl7pRpciyCPIhtr1122Hrwf0L5dpSdQ=; b=fRdoNz7o3TloqXbDEDOmiFvu4ljRIhGrdaCv5EPQCTGKIZSYzflDfor7DAQOpf1k2O mvA4boEUskxmQqoWra9gOqFyFekOYN5TIYdkatjoB+4A6lLjFQpFVw8VdFDQNAAmAfCz +tWKrO/HiX7G86KrxkchkxeBeFMw2JkokQIkPrGvihDUKwcpYrRercIr6es/GXyWu3Ja 9u5K2vPVDWflMl4c2Qmj4aP5JU2wF1JEB0eL1QrjKnyWwB5kOjKnMU8HhRcin6lSQTH2 XhUvQOjXLyfTJlcA6BjYnfsdPrMVicMsmJSQQS7lknitm30bwTx65IkpLzU3qbWfjlaX 8wsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=s1+/v0bKB40agl7pRpciyCPIhtr1122Hrwf0L5dpSdQ=; b=J5LJXYagyoYGiCmwdNLx/S11cfdkN1qJoXymzVAOQPTjyE7k1JPL16ERhdZKLedYaB U5ifOGgOhvS3ceTVMR8v5w27WSm+hhq7BzKBJnwwtATcfYDAH16TL22YSlu7S9S23Mh5 IUWravVIfzOZLQD+ZibFzha+FnD/sDR4OE9Dp58ssCNLyPahoZTsb9b37LiBUmn8TkPp lcItziqr/4HYGo1NcfDdJMfaToJ7b7DoQrO4PBSahn0ysFRZidtF0GNm6ukn8Y5FkxJp tXCbhzMedREk+rx0YLTPvMmCN684zyhbpmwy9Gc/NeSTECjVXao2v5AVht17n945QQuy Yd4A== X-Gm-Message-State: AElRT7EtQkDTGEykkA0356m9bWnl7wyfvjMxXS/DjZ0WAplXd8UL2wwG hJOaan3htWgVEV4vH0gcRqhwGw== X-Received: by 10.223.184.56 with SMTP id h53mr9248886wrf.87.1522408678784; Fri, 30 Mar 2018 04:17:58 -0700 (PDT) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id b34sm17692634wra.21.2018.03.30.04.17.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 30 Mar 2018 04:17:58 -0700 (PDT) Date: Fri, 30 Mar 2018 13:17:56 +0200 From: Ingo Molnar To: Waiman Long Cc: Ingo Molnar , Peter Zijlstra , Thomas Gleixner , linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: Re: [PATCH v4 2/2] locking/debug: Restructure the lock debugging menu Message-ID: <20180330111756.jvikchnxaeqkojao@gmail.com> References: <1522246852-17501-1-git-send-email-longman@redhat.com> <1522246852-17501-3-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1522246852-17501-3-git-send-email-longman@redhat.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Waiman Long wrote: > Two config options in the lock debugging menu that are probably the most > frequently used, as far as I am concerned, is the PROVE_LOCKING and > LOCK_STAT. From a UI perspective, they should be front and center. So > these two options are now moved to the top of the lock debugging menu. > > The DEBUG_WW_MUTEX_SLOWPATH option is also added to the PROVE_LOCKING > umbrella. > > Signed-off-by: Waiman Long > --- > lib/Kconfig.debug | 146 ++++++++++++++++++++++++++++-------------------------- > 1 file changed, 76 insertions(+), 70 deletions(-) > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 6aad28c..dc9ffe2 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1034,6 +1034,79 @@ config DEBUG_PREEMPT > > menu "Lock Debugging (spinlocks, mutexes, etc...)" > > +config LOCK_DEBUGGING_SUPPORT > + bool > + depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT > + default y Ok, this patch is a nice reorganization - but could we please split this into two patches, the first one adds the LOCK_DEBUGGING_SUPPORT helper, the other does the reordering of the entries (without changing anything in the entries)? It's hard to review when the two steps are mixed up. Thanks, Ingo