* [PATCH] ktest.pl minconfig: Unset configs instead of just removing them
@ 2022-12-02 16:59 Steven Rostedt
2022-12-02 21:40 ` John 'Warthog9' Hawley
0 siblings, 1 reply; 2+ messages in thread
From: Steven Rostedt @ 2022-12-02 16:59 UTC (permalink / raw)
To: LKML; +Cc: John 'Warthog9' Hawley
From: Steven Rostedt <rostedt@goodmis.org>
After a full run of a make_min_config test, I noticed there were a lot of
CONFIGs still enabled that really should not be. Looking at them, I
noticed they were all defined as "default y". The issue is that the test
simple removes the config and re-runs make oldconfig, which enables it
again because it is set to default 'y'. Instead, explicitly disable the
config with writing "# CONFIG_FOO is not set" to the file to keep it from
being set again.
With this change, one of my box's minconfigs went from 768 configs set,
down to 521 configs set.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
tools/testing/ktest/ktest.pl | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 590518144167..56135e7d2295 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -3775,9 +3775,10 @@ sub test_this_config {
# .config to make sure it is missing the config that
# we had before
my %configs = %min_configs;
- delete $configs{$config};
+ $configs{$config} = "# $config is not set";
make_new_config ((values %configs), (values %keep_configs));
make_oldconfig;
+ delete $configs{$config};
undef %configs;
assign_configs \%configs, $output_config;
--
2.35.1
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] ktest.pl minconfig: Unset configs instead of just removing them
2022-12-02 16:59 [PATCH] ktest.pl minconfig: Unset configs instead of just removing them Steven Rostedt
@ 2022-12-02 21:40 ` John 'Warthog9' Hawley
0 siblings, 0 replies; 2+ messages in thread
From: John 'Warthog9' Hawley @ 2022-12-02 21:40 UTC (permalink / raw)
To: Steven Rostedt, LKML
On 12/2/22 08:59, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> After a full run of a make_min_config test, I noticed there were a lot of
> CONFIGs still enabled that really should not be. Looking at them, I
> noticed they were all defined as "default y". The issue is that the test
> simple removes the config and re-runs make oldconfig, which enables it
> again because it is set to default 'y'. Instead, explicitly disable the
> config with writing "# CONFIG_FOO is not set" to the file to keep it from
> being set again.
>
> With this change, one of my box's minconfigs went from 768 configs set,
> down to 521 configs set.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
> tools/testing/ktest/ktest.pl | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
> index 590518144167..56135e7d2295 100755
> --- a/tools/testing/ktest/ktest.pl
> +++ b/tools/testing/ktest/ktest.pl
> @@ -3775,9 +3775,10 @@ sub test_this_config {
> # .config to make sure it is missing the config that
> # we had before
> my %configs = %min_configs;
> - delete $configs{$config};
> + $configs{$config} = "# $config is not set";
> make_new_config ((values %configs), (values %keep_configs));
> make_oldconfig;
> + delete $configs{$config};
> undef %configs;
> assign_configs \%configs, $output_config;
>
Reviewed-by: John 'Warthog9' Hawley (VMware) <warthog9@eaglescrag.net>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-12-02 21:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-02 16:59 [PATCH] ktest.pl minconfig: Unset configs instead of just removing them Steven Rostedt
2022-12-02 21:40 ` John 'Warthog9' Hawley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®