All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Philip Auld <pauld@redhat.com>, ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime
Date: Tue, 26 Nov 2024 12:23:30 +0100	[thread overview]
Message-ID: <Z0Wvsq571rTt46Ie@yuki.lan> (raw)
In-Reply-To: <CAEemH2cpYA28nknKOhNV0D4q8G+xPw6EuvScMHbgOO3jpRPv7w@mail.gmail.com>

Hi!
> Well, we have not achieved a reliable way to detect debug kernels in LTP.
> While I looking at our RHEL9 kernel config file. The general kernel also
> enables things like "CONFIG_DEBUG_KERNEL=y".

The slowdown is likely to be realated to a few specific debug options
such as debugging for mutexes, spinlocks, lists, etc. I guess that the
most interesting information would be a difference in the debug options
between the general kernel and the debug kernel. Hopefully we can put
together a set of debug options that are cause the test to run over
slow.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-11-26 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 10:04 [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Li Wang
2024-11-26 10:28 ` Cyril Hrubis
2024-11-26 10:59   ` Li Wang
2024-11-26 11:23     ` Cyril Hrubis [this message]
2024-11-27  4:15       ` Li Wang
2024-11-27  7:48         ` [LTP] [Draft PATCH] lib: add TST_DYNAMICAL_RUNTIME option Li Wang
2024-11-27  8:21           ` Li Wang
2024-11-27  9:46         ` [LTP] [RFC PATCH] starvation: set a baseline for maximum runtime Cyril Hrubis
2024-11-27 10:08           ` Li Wang
2024-11-27 10:40             ` Cyril Hrubis
2024-11-27 10:56               ` Li Wang

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=Z0Wvsq571rTt46Ie@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=pauld@redhat.com \
    /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.