public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Markus Ongyerth <markus@ongy.net>
Cc: linux-rt-users@vger.kernel.org, ongyerth@intrinsic.ai,
	cschiemann@intrinsic.ai
Subject: Re: Ist drm/i915: Depend on !PREEMPT_RT. still necessary?
Date: Thu, 12 Mar 2026 12:31:56 +0100	[thread overview]
Message-ID: <20260312113156.yINqVd8t@linutronix.de> (raw)
In-Reply-To: <4b7478ba-e10e-4877-b2e6-63203ffa9094@app.fastmail.com>

On 2026-02-02 17:16:00 [+0100], Markus Ongyerth wrote:
> Hi,

Hi,

> in https://patchwork.kernel.org/project/intel-gfx/patch/YgqmfKhwU5spS069@linutronix.de/#24761794 the i915 module was disabled for RT_PREEMPT kernels.
> The associated discussion mentions that it shuld be save to revert this once more patches have made it in.
> From what I can see, further patches did make it in. But the dependency is still there.
> 
> Was this an oversight or is it still unsafe to use i915 with
> RT_PREEMPT? If the latter, is there a patchset we could pull to make
> it safer? Or is there some place to read up on the dangers?

If you look at the latest 7.0.-RT queue, there are still i915 patches in
it. It is not an oversight. There is this series
	https://lore.kernel.org/all/20260310115709.2276203-1-dev@lankhorst.se/

which once landed would get rid of this !RT for i915.

> Thanks,
> Markus

Sebastian

      reply	other threads:[~2026-03-12 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 16:16 Ist drm/i915: Depend on !PREEMPT_RT. still necessary? Markus Ongyerth
2026-03-12 11:31 ` Sebastian Andrzej Siewior [this message]

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=20260312113156.yINqVd8t@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=cschiemann@intrinsic.ai \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=markus@ongy.net \
    --cc=ongyerth@intrinsic.ai \
    /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