From: Dave Hansen <dave.hansen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>, Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH] [RFC] Documentation/process: Add testing section to tip handbook
Date: Mon, 14 Mar 2022 11:35:52 -0700 [thread overview]
Message-ID: <20220314183552.1446911-1-dave.hansen@linux.intel.com> (raw)
From: Dave Hansen <dave.hansen@linux.intel.com>
The kernel has a wide variety of debugging options to help catch
and squash bugs. However, new debugging is added all the time and
the existing options can be hard to find.
Add a list of debugging options which tip maintainers expect to be
used to test contributions.
This should make it easier for contributors to test their code and
find issues before submission.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Borislav Petkov <bp@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: x86@kernel.org
Cc: linux-doc@vger.kernel.org
---
Documentation/process/maintainer-tip.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/Documentation/process/maintainer-tip.rst b/Documentation/process/maintainer-tip.rst
index c74f4a81588b..75f86b0f1cf0 100644
--- a/Documentation/process/maintainer-tip.rst
+++ b/Documentation/process/maintainer-tip.rst
@@ -437,6 +437,30 @@ in a private repository which allows interested people to easily pull the
series for testing. The usual way to offer this is a git URL in the cover
letter of the patch series.
+Testing
+^^^^^^^
+
+Code should be tested before submitting to the tip maintainers. Anything
+other than minor changes should be built, booted and tested with the
+following set of comprehensive (and heavyweight) set of kernel debugging
+options enabled.
+
+ CONFIG_X86_DEBUG_FPU=y
+ CONFIG_LOCK_STAT=y
+ CONFIG_DEBUG_VM=y
+ CONFIG_DEBUG_VM_VMACACHE=y
+ CONFIG_DEBUG_VM_RB=y
+ CONFIG_DEBUG_SLAB=y
+ CONFIG_DEBUG_KMEMLEAK=y
+ CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_SLUB_DEBUG_ON=y
+ CONFIG_KMEMCHECK=y
+ CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=y
+ CONFIG_GCOV_KERNEL=y
+ CONFIG_LOCKDEP=y
+ CONFIG_PROVE_LOCKING=y
+ CONFIG_SCHEDSTATS=y
+ CONFIG_VMLINUX_VALIDATION=y
Coding style notes
------------------
--
2.34.0
next reply other threads:[~2022-03-14 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 18:35 Dave Hansen [this message]
2022-03-31 12:38 ` [PATCH] [RFC] Documentation/process: Add testing section to tip handbook Borislav Petkov
2022-03-31 17:37 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220314183552.1446911-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).