From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] [RFC] Documentation/process: Add testing section to tip handbook
Date: Thu, 31 Mar 2022 10:37:30 -0700 [thread overview]
Message-ID: <2444feb5-3c61-3d90-c57a-84c40849cd67@intel.com> (raw)
In-Reply-To: <YkWgv1yBGtcAbPVj@zn.tnic>
On 3/31/22 05:38, Borislav Petkov wrote:
>> +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
...
> It would be cool if there were a command I can run so that I can enable
> all those. Example:
>
> $ grep CONFIG_VMLINUX_VALIDATION .config
> $ ./scripts/config --enable CONFIG_VMLINUX_VALIDATION
> $ grep CONFIG_VMLINUX_VALIDATION .config
> CONFIG_VMLINUX_VALIDATION=y
> $ make oldconfig
> #
> # configuration written to .config
> #
> $ grep CONFIG_VMLINUX_VALIDATION .config
> $
>
> Needs other options.
>
> Maybe you could create a .config snippet which we can merge
> with scripts/kconfig/merge_config.sh... or maybe start from
> arch/x86/configs/x86_64_defconfig, add all those and call it
>
> arch/x86/configs/x86_64_testconfig
Well, after some digging around it turns out that we're not the first
ones with this problem. Just throwing those options into:
kernel/configs/x86_debug.config
and doing:
make x86_debug.config
will magically do:
Using .config as base
Merging /home/davehans/linux.git/kernel/configs/x86_debug.config
#
# merged configuration written to .config (needs make)
...
Who knew? I'll move the options and send another patch.
prev parent reply other threads:[~2022-03-31 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 18:35 [PATCH] [RFC] Documentation/process: Add testing section to tip handbook Dave Hansen
2022-03-31 12:38 ` Borislav Petkov
2022-03-31 17:37 ` 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:
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=2444feb5-3c61-3d90-c57a-84c40849cd67@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--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).