public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: "Markus Ongyerth" <markus@ongy.net>
To: linux-rt-users@vger.kernel.org
Cc: ongyerth@intrinsic.ai, cschiemann@intrinsic.ai
Subject: Ist drm/i915: Depend on !PREEMPT_RT. still necessary?
Date: Mon, 02 Feb 2026 17:16:00 +0100	[thread overview]
Message-ID: <4b7478ba-e10e-4877-b2e6-63203ffa9094@app.fastmail.com> (raw)

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?

Thanks,
Markus

             reply	other threads:[~2026-02-02 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 16:16 Markus Ongyerth [this message]
2026-03-12 11:31 ` Ist drm/i915: Depend on !PREEMPT_RT. still necessary? 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=4b7478ba-e10e-4877-b2e6-63203ffa9094@app.fastmail.com \
    --to=markus@ongy.net \
    --cc=cschiemann@intrinsic.ai \
    --cc=linux-rt-users@vger.kernel.org \
    --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