From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@linutronix.de
Cc: mingo@kernel.org, peterz@infradead.org, bigeasy@linutronix.de,
dave@stgolabs.net, linux-rt-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH -tip 0/2] kernel/hrtimer: Ignore slack time for RT tasks
Date: Mon, 23 Jan 2023 09:32:04 -0800 [thread overview]
Message-ID: <20230123173206.6764-1-dave@stgolabs.net> (raw)
Hi,
Patch 2 simply ignores any user passed slack time in the case of RT/DL
tasks for schedule_hrtimeout_range, which is aligned to what nanosleep(2)
already does.
Thanks!
Davidlohr Bueso (2):
kernel/hrtimer: Rely on rt_task() for DL tasks too
kernel/hrtimer: Ignore slack time for RT tasks
kernel/time/hrtimer.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-23 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 17:32 Davidlohr Bueso [this message]
2023-01-23 17:32 ` [PATCH 1/2] kernel/hrtimer: Rely on rt_task() for DL tasks too Davidlohr Bueso
2023-01-31 10:24 ` Thomas Gleixner
2023-01-23 17:32 ` [PATCH 2/2] kernel/hrtimer: Ignore slack time for RT tasks Davidlohr Bueso
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=20230123173206.6764-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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