All of
 help / color / mirror / Atom feed
From: "tip-bot2 for Dave Hansen" <>
Cc: Dave Hansen <>,
	Borislav Petkov <>,,
Subject: [tip: x86/build] x86/configs: Add x86 debugging Kconfig fragment plus docs
Date: Wed, 06 Apr 2022 18:01:04 -0000	[thread overview]
Message-ID: <164926806495.389.2039548073927168895.tip-bot2@tip-bot2> (raw)
In-Reply-To: <>

The following commit has been merged into the x86/build branch of tip:

Commit-ID:     9b5a7f4a2a8dcda461f9c7a6671150f4a8a902e8
Author:        Dave Hansen <>
AuthorDate:    Thu, 31 Mar 2022 10:57:28 -07:00
Committer:     Borislav Petkov <>
CommitterDate: Wed, 06 Apr 2022 19:56:29 +02:00

x86/configs: Add x86 debugging Kconfig fragment plus docs

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 Kconfig fragment with the 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.

  [ bp: Add to "make help" output, fix DEBUG_INFO selection as pointed
        out by Nathan Chancellor <>. ]

Signed-off-by: Dave Hansen <>
Signed-off-by: Borislav Petkov <>
 Documentation/process/maintainer-tip.rst | 14 ++++++++++++++
 arch/x86/Makefile                        |  1 +
 kernel/configs/x86_debug.config          | 18 ++++++++++++++++++
 3 files changed, 33 insertions(+)
 create mode 100644 kernel/configs/x86_debug.config

diff --git a/Documentation/process/maintainer-tip.rst b/Documentation/process/maintainer-tip.rst
index c74f4a8..572a328 100644
--- a/Documentation/process/maintainer-tip.rst
+++ b/Documentation/process/maintainer-tip.rst
@@ -437,6 +437,20 @@ 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.
+Code should be tested before submitting to the tip maintainers.  Anything
+other than minor changes should be built, booted and tested with
+comprehensive (and heavyweight) kernel debugging options enabled.
+These debugging options can be found in kernel/configs/x86_debug.config
+and can be added to an existing kernel config by running:
+	make x86_debug.config
+Some of these options are x86-specific and can be left out when testing
+on other architectures.
 Coding style notes
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 63d50f6..1abd7cc 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -313,5 +313,6 @@ define archhelp
   echo  ''
   echo  '  kvm_guest.config	- Enable Kconfig items for running this kernel as a KVM guest'
   echo  '  xen.config		- Enable Kconfig items for running this kernel as a Xen guest'
+  echo  '  x86_debug.config	- Enable tip tree debugging options for testing'
diff --git a/kernel/configs/x86_debug.config b/kernel/configs/x86_debug.config
new file mode 100644
index 0000000..dcd86f3
--- /dev/null
+++ b/kernel/configs/x86_debug.config
@@ -0,0 +1,18 @@

      parent reply	other threads:[~2022-04-06 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 17:57 [PATCH] [v2] x86/configs: Add x86 debugging Kconfig fragment plus docs Dave Hansen
2022-03-31 17:57 ` Dave Hansen
2022-04-01 17:57 ` Borislav Petkov
2022-04-05 20:01 ` [tip: x86/build] " tip-bot2 for Dave Hansen
2022-04-06 16:55   ` Nathan Chancellor
2022-04-06 17:59     ` Borislav Petkov
2022-04-06 18:01 ` tip-bot2 for Dave Hansen [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=164926806495.389.2039548073927168895.tip-bot2@tip-bot2 \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.