Date:   Wed, 10 Nov 2021 16:52:19 -0500
From:   Qian Cai <quic_qiancai@quicinc.com>
To:     Andrew Morton <akpm@linux-foundation.org>,
        Masahiro Yamada <masahiroy@kernel.org>,
        Daniel Thompson <daniel.thompson@linaro.org>
CC:     <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] configs: Introduce debug.config for CI-like setup
Message-ID: <YYw/E1hIQWfWJD3I@qian-HP-Z2-SFF-G5-Workstation>
References: <20211104161504.11806-1-quic_qiancai@quicinc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20211104161504.11806-1-quic_qiancai@quicinc.com>
Precedence: bulk

On Thu, Nov 04, 2021 at 12:15:04PM -0400, Qian Cai wrote:
> Some general debugging features like kmemleak, KASAN, lockdep, UBSAN etc
> help fix many viruses like a microscope. On the other hand, those features
> are scatter around and mixed up with more situational debugging options
> making them difficult to consume properly. This cold help amplify the
> general debugging/testing efforts and help establish sensitive default
> values for those options across the broad.
> 
> The config is based on years' experiences running daily CI inside the
> largest enterprise Linux distro company to seek regressions on
> linux-next builds on different bare-metal and virtual platforms. It can be
> used for example,
> 
> $ make ARCH=arm64 defconfig debug.config

Andrew, can you take a look at this patch?