linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Michael Schanne <michael.schanne@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: liveloock using PREEMPT_RT with i915 driver
Date: Wed, 18 Jun 2025 14:16:56 +0200	[thread overview]
Message-ID: <20250618121656.wjpoNGAT@linutronix.de> (raw)
In-Reply-To: <CAC_kJhQZpZoUjavRsSVHuXL5k3-3u6+wdL9=h8Pbv3qWvzeOiw@mail.gmail.com>

On 2025-06-18 07:34:25 [-0400], Michael Schanne wrote:
> I found my issue, I am using several SCHED_FIFO threads, one was spinning
> waiting on a timer to update, another thread which was supposed to update
> the timer count is higher priority, but with the RT patch applied there is
> also a ktimers thread set to RT priority 1, so it was never getting a
> chance to run and my timer would never fire.  I adjusted the ktimers thread
> to a higher priority and things started working again.  This thread does
> not exist in the vanilla kernel even with CONFIG_PREEMPT_RT enabled, so
> that is why I wasn't seeing it there.  The i915 driver was a red herring.

Okay not the i915.
The ktimers thread wakes only SCHED_OTHER tasks. The SCHED_FIFO/RR
threads should be woken up directly (without the need of the ktimers
thread).
So you are not using clock_nanosleep() but something like a POSIX timer?

> Thanks,
> Mike

Sebastian

  parent reply	other threads:[~2025-06-18 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  2:06 liveloock using PREEMPT_RT with i915 driver Michael Schanne
2025-06-17 10:05 ` Sebastian Andrzej Siewior
     [not found]   ` <CAC_kJhQZpZoUjavRsSVHuXL5k3-3u6+wdL9=h8Pbv3qWvzeOiw@mail.gmail.com>
2025-06-18 12:16     ` Sebastian Andrzej Siewior [this message]
2025-06-19 11:19       ` Michael Schanne
2025-06-20  8:16         ` Sebastian Andrzej Siewior

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=20250618121656.wjpoNGAT@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=michael.schanne@gmail.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;
as well as URLs for NNTP newsgroup(s).