mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Christian Loehle" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Christian Loehle <christian.loehle@arm.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/deadline: Convert schedtool example to chrt
Date: Tue, 10 Sep 2024 08:09:21 -0000	[thread overview]
Message-ID: <172595576198.2215.14641067488346497218.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240813144348.1180344-2-christian.loehle@arm.com>

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     e031b586326f7d3d6be70dd1d69ed3045d9506ca
Gitweb:        https://git.kernel.org/tip/e031b586326f7d3d6be70dd1d69ed3045d9506ca
Author:        Christian Loehle <christian.loehle@arm.com>
AuthorDate:    Tue, 13 Aug 2024 15:43:45 +01:00
Committer:     Peter Zijlstra <peterz@infradead.org>
CommitterDate: Tue, 10 Sep 2024 09:51:16 +02:00

sched/deadline: Convert schedtool example to chrt

chrt has SCHED_DEADLINE support so convert the example instead of
relying on a schedtool fork. While at it fix the wrong mentioning
of microseconds, it was nanoseconds for both schedtool and chrt.

Signed-off-by: Christian Loehle <christian.loehle@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Juri Lelli <juri.lelli@redhat.com>
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
Link: https://lore.kernel.org/r/20240813144348.1180344-2-christian.loehle@arm.com
---
 Documentation/scheduler/sched-deadline.rst | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/Documentation/scheduler/sched-deadline.rst b/Documentation/scheduler/sched-deadline.rst
index 9fe4846..22838ed 100644
--- a/Documentation/scheduler/sched-deadline.rst
+++ b/Documentation/scheduler/sched-deadline.rst
@@ -749,21 +749,19 @@ Appendix A. Test suite
  of the command line options. Please refer to rt-app documentation for more
  details (`<rt-app-sources>/doc/*.json`).
 
- The second testing application is a modification of schedtool, called
- schedtool-dl, which can be used to setup SCHED_DEADLINE parameters for a
- certain pid/application. schedtool-dl is available at:
- https://github.com/scheduler-tools/schedtool-dl.git.
+ The second testing application is done using chrt which has support
+ for SCHED_DEADLINE.
 
  The usage is straightforward::
 
-  # schedtool -E -t 10000000:100000000 -e ./my_cpuhog_app
+  # chrt -d -T 10000000 -D 100000000 0 ./my_cpuhog_app
 
  With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation
- of 10ms every 100ms (note that parameters are expressed in microseconds).
- You can also use schedtool to create a reservation for an already running
+ of 10ms every 100ms (note that parameters are expressed in nanoseconds).
+ You can also use chrt to create a reservation for an already running
  application, given that you know its pid::
 
-  # schedtool -E -t 10000000:100000000 my_app_pid
+  # chrt -d -T 10000000 -D 100000000 -p 0 my_app_pid
 
 Appendix B. Minimal main()
 ==========================

  reply	other threads:[~2024-09-10  8:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 14:43 [PATCH 0/4] sched/deadline: nanoseconds clarifications Christian Loehle
2024-08-13 14:43 ` [PATCH 1/4] sched/deadline: Convert schedtool example to chrt Christian Loehle
2024-09-10  8:09   ` tip-bot2 for Christian Loehle [this message]
2024-09-11  9:32   ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 2/4] sched/deadline: Clarify nanoseconds in uapi Christian Loehle
2024-09-10  8:09   ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11  9:32   ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 3/4] cpufreq/cppc: Use NSEC_PER_MSEC for deadline task Christian Loehle
2024-09-10  8:09   ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11  9:32   ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 4/4] sched/cpufreq: " Christian Loehle
2024-09-09 13:38   ` Vincent Guittot
2024-09-10  8:09   ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11  9:32   ` tip-bot2 for Christian Loehle
2024-08-13 16:02 ` [PATCH 0/4] sched/deadline: nanoseconds clarifications Juri Lelli
2024-09-09 13:01   ` Christian Loehle
2024-09-09 13:25     ` Peter Zijlstra
2024-09-09 16:39       ` Rafael J. Wysocki

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=172595576198.2215.14641067488346497218.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=christian.loehle@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --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

all inboxes | Powered by JetHome®