From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs
Date: Mon, 16 Dec 2024 14:00:21 +0100 [thread overview]
Message-ID: <Z2AkZabEU12gomtZ@yuki.lan> (raw)
In-Reply-To: <20241213224041.GB1577592@pevik>
Hi!
> > + TST_KCONFIG_INIT("CONFIG_KASAN"),
> > + TST_KCONFIG_INIT("CONFIG_SLUB_RCU_DEBUG"),
> > + TST_KCONFIG_INIT("CONFIG_TRACE_IRQFLAGS"),
> > + TST_KCONFIG_INIT("CONFIG_LATENCYTOP"),
> > + TST_KCONFIG_INIT("CONFIG_DEBUG_NET"),
> > + TST_KCONFIG_INIT("CONFIG_EXT4_DEBUG"),
> > + TST_KCONFIG_INIT("CONFIG_QUOTA_DEBUG"),
> > + TST_KCONFIG_INIT("CONFIG_FAULT_INJECTION"),
> > + TST_KCONFIG_INIT("CONFIG_DEBUG_OBJECTS")
> > +};
> > +
> > +int tst_has_slow_kconfig(void)
> > +{
> > + unsigned int i;
> > +
> > + tst_kconfig_read(slow_kconfigs, ARRAY_SIZE(slow_kconfigs));
> > +
> Maybe here TINFO message "checking for options which slow the execution?
> Or print it (once) only if option detected? Because it's not obvious why we are
> detecting it. Or after searching print what we did (4x prolonged runtime).
>
> > + for (i = 0; i < ARRAY_SIZE(slow_kconfigs); i++) {
> > + if (slow_kconfigs[i].choice == 'y') {
> > + tst_res(TINFO,
> > + "%s kernel option detected",
> > + slow_kconfigs[i].id);
> > + return 1;
> > + }
> > + }
> > +
> > + return 0;
> > +}
> > diff --git a/lib/tst_test.c b/lib/tst_test.c
> > index 8db554dea..f4e667240 100644
> > --- a/lib/tst_test.c
> > +++ b/lib/tst_test.c
> > @@ -555,6 +555,9 @@ static int multiply_runtime(int max_runtime)
>
> > parse_mul(&runtime_mul, "LTP_RUNTIME_MUL", 0.0099, 100);
>
> > + if (tst_has_slow_kconfig())
> > + max_runtime *= 4;
> Maybe note here what we do? (TINFO)
That really depends on how verbose we want to be, we already print the
overall test timeout which is timeout + runtime. So it's somehow visible
in the test runtime has been increased. Maybe we should make the info
message in set_timeout() better by printing the runtime separately there
if non-zero.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-12-16 13:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 6:04 [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs Li Wang
2024-12-13 22:40 ` Petr Vorel
2024-12-16 9:37 ` Li Wang
2024-12-16 12:28 ` Petr Vorel
2024-12-17 2:40 ` Li Wang
2024-12-16 13:00 ` Cyril Hrubis [this message]
2024-12-16 17:29 ` Petr Vorel
2024-12-17 3:46 ` Li Wang
2024-12-18 3:23 ` Li Wang
2024-12-16 12:51 ` Cyril Hrubis
2024-12-19 12:53 ` Petr Vorel
2024-12-19 13:07 ` Li Wang
2024-12-19 12:57 ` Martin Doucha
2024-12-19 13:07 ` Petr Vorel
2024-12-19 13:12 ` Li Wang
2024-12-19 13:28 ` Petr Vorel
2024-12-19 13:29 ` Cyril Hrubis
2024-12-20 3:59 ` Li Wang
2024-12-20 7:19 ` Li Wang
2024-12-19 13:10 ` Cyril Hrubis
2024-12-19 13:14 ` Li Wang
2024-12-19 13:19 ` Cyril Hrubis
2024-12-19 13:22 ` Li Wang
2024-12-19 13:25 ` Petr Vorel
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=Z2AkZabEU12gomtZ@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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 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.