From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
Thomas Gleixner <tglx@linutronix.de>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Depend on !PREEMPT_RT.
Date: Mon, 28 Feb 2022 10:10:48 +0000 [thread overview]
Message-ID: <474ded6f-4fe8-8355-9a96-2254401d10fc@linux.intel.com> (raw)
In-Reply-To: <YhlgRb1lZO38gAz5@linutronix.de>
Hi,
On 25/02/2022 23:03, Sebastian Andrzej Siewior wrote:
> On 2022-02-14 19:59:08 [+0100], To intel-gfx@lists.freedesktop.org wrote:
>> There are a few sections in the driver which are not compatible with
>> PREEMPT_RT. They trigger warnings and can lead to deadlocks at runtime.
>>
>> Disable the i915 driver on a PREEMPT_RT enabled kernel. This way
>> PREEMPT_RT itself can be enabled without needing to address the i915
>> issues first. The RT related patches are still in RT queue and will be
>> handled later.
>>
>> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> A gentle ping ;)
Could you paste a link to the queue of i915 patches pending for a quick
overview of how much work there is and in what areas?
Also, I assume due absence of ARCH_SUPPORTS_RT being defined by any
arch, that something more is not yet ready?
Regards,
Tvrtko
>> ---
>> drivers/gpu/drm/i915/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/i915/Kconfig b/drivers/gpu/drm/i915/Kconfig
>> index a4c94dc2e2164..3aa719d5a0f0d 100644
>> --- a/drivers/gpu/drm/i915/Kconfig
>> +++ b/drivers/gpu/drm/i915/Kconfig
>> @@ -3,6 +3,7 @@ config DRM_I915
>> tristate "Intel 8xx/9xx/G3x/G4x/HD Graphics"
>> depends on DRM
>> depends on X86 && PCI
>> + depends on !PREEMPT_RT
>> select INTEL_GTT
>> select INTERVAL_TREE
>> # we need shmfs for the swappable backing store, and in particular
>
> Sebastian
next prev parent reply other threads:[~2022-02-28 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 18:59 [Intel-gfx] [PATCH] drm/i915: Depend on !PREEMPT_RT Sebastian Andrzej Siewior
2022-02-16 3:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-02-16 7:16 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-02-25 23:03 ` [Intel-gfx] [PATCH] " Sebastian Andrzej Siewior
2022-02-28 10:10 ` Tvrtko Ursulin [this message]
2022-02-28 10:35 ` Sebastian Andrzej Siewior
2022-03-01 14:27 ` Tvrtko Ursulin
2022-03-01 15:13 ` Sebastian Andrzej Siewior
2022-03-02 11:42 ` Tvrtko Ursulin
2022-03-02 12:32 ` 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=474ded6f-4fe8-8355-9a96-2254401d10fc@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=airlied@linux.ie \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--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