public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: John Stultz via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: kernel-team@android.com, John Stultz <jstultz@google.com>,
	Darren Hart <darren@os.amperecomputing.com>
Subject: [LTP] [PATCH v2 0/6] sched_football: Re-add crazy fans and other cleanups
Date: Tue, 25 Jun 2024 16:52:29 -0700	[thread overview]
Message-ID: <20240625235245.2106313-1-jstultz@google.com> (raw)

Just the other day (~18 years ago), I had implemented the
sched_football test to validate the RT scheduling invariant that
we always run the top NR_CPU priority tasks at any time.

That early version of the test included crazy fans, which
disrupted the scheduling of the defensive threads. This was
later removed from the test, likely due to occasional failures
seen with it.

Recently, in testing the behavior of a scheduler patch I was
working on I started tinkering with this test again, and found
when I re-added the crazy fans, I could reproduce an actual
scheduling problem with the vanilla kernel.

So I wanted to submit these changes to re-add the crazy fans
along with some other cleanups and improvements to make it
easier to use with tracing, so that the test can be used by
others to reproduce this problem.

New in v2 (thank you for the feedback!):
* Rework to use tst_atomic* methods instead of atomic_t
  suggested by Cyril
* Remove unused variables
* Drop changelog comment as suggested by Cyril
* Rework to use tst_atomic_* functions as suggested by Cyril
* Rework to use tst_timespec* functions as suggested by Cyril
* Pulled trace marker writing out into librttest helper functions
  as suggested by Cyril

thanks
-john

Cc: kernel-team@android.com
Cc: Cyril Hrubis <chrubis@suse.cz>
Cc: Darren Hart <darren@os.amperecomputing.com>


John Stultz (6):
  sched_football: Drop use of sched_yeild()
  sched_football: Use atomic operations for ball
  sched_football: Re-add the crazy fans to interrupt everyone
  sched_football: Add a sleep before the game begins to get into steady
    state
  sched_football: Add prctrl calls to set thread comms
  sched_football: Add trace_marker messages if we're tracing

 .../func/sched_football/sched_football.c      | 95 +++++++++++++++----
 testcases/realtime/include/librttest.h        | 13 +++
 testcases/realtime/lib/librttest.c            | 32 +++++++
 3 files changed, 119 insertions(+), 21 deletions(-)

-- 
2.45.2.741.gdbec12cfda-goog


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

             reply	other threads:[~2024-06-25 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 23:52 John Stultz via ltp [this message]
2024-06-25 23:52 ` [LTP] [PATCH v2 1/6] sched_football: Drop use of sched_yeild() John Stultz via ltp
2024-06-25 23:52 ` [LTP] [PATCH v2 2/6] sched_football: Use atomic operations for ball John Stultz via ltp
2024-06-25 23:52 ` [LTP] [PATCH v2 3/6] sched_football: Re-add the crazy fans to interrupt everyone John Stultz via ltp
2024-06-25 23:52 ` [LTP] [PATCH v2 4/6] sched_football: Add a sleep before the game begins to get into steady state John Stultz via ltp
2024-06-25 23:52 ` [LTP] [PATCH v2 5/6] sched_football: Add prctrl calls to set thread comms John Stultz via ltp
2024-06-25 23:52 ` [LTP] [PATCH v2 6/6] sched_football: Add trace_marker messages if we're tracing John Stultz via ltp
2024-06-26 11:49 ` [LTP] [PATCH v2 0/6] sched_football: Re-add crazy fans and other cleanups Cyril Hrubis

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=20240625235245.2106313-1-jstultz@google.com \
    --to=ltp@lists.linux.it \
    --cc=darren@os.amperecomputing.com \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox