All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>
Cc: <intel-gfx@lists.freedesktop.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Subject: Re: [PATCH 2/4] drm/i915: Drop the irqs_disabled() check
Date: Tue, 15 Jul 2025 15:08:26 -0400	[thread overview]
Message-ID: <aHanKmYpOt-4XXOv@intel.com> (raw)
In-Reply-To: <20250715154125.27813-8-dev@lankhorst.se>

On Tue, Jul 15, 2025 at 05:41:28PM +0200, Maarten Lankhorst wrote:
> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> 
> The !irqs_disabled() check triggers on PREEMPT_RT even with
> i915_sched_engine::lock acquired. The reason is the lock is transformed
> into a sleeping lock on PREEMPT_RT and does not disable interrupts.
> 
> There is no need to check for disabled interrupts. The lockdep
> annotation below already check if the lock has been acquired by the
> caller and will yell if the interrupts are not disabled.
> 
> Remove the !irqs_disabled() check.
> 
> Reported-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Acked-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Link: https://lore.kernel.org/r/20250714153954.629393-7-bigeasy@linutronix.de
> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/i915/i915_request.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index c3d27eadc0a7e..4705d6d6db141 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -608,7 +608,6 @@ bool __i915_request_submit(struct i915_request *request)
>  
>  	RQ_TRACE(request, "\n");
>  
> -	GEM_BUG_ON(!irqs_disabled());
>  	lockdep_assert_held(&engine->sched_engine->lock);
>  
>  	/*
> @@ -717,7 +716,6 @@ void __i915_request_unsubmit(struct i915_request *request)
>  	 */
>  	RQ_TRACE(request, "\n");
>  
> -	GEM_BUG_ON(!irqs_disabled());
>  	lockdep_assert_held(&engine->sched_engine->lock);
>  
>  	/*
> -- 
> 2.45.2
> 

  reply	other threads:[~2025-07-15 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 15:41 [PATCH 0/4] CI test the -gt-next patches Maarten Lankhorst
2025-07-15 15:41 ` [PATCH 1/4] drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() + spin_lock() Maarten Lankhorst
2025-07-15 15:41 ` [PATCH 2/4] drm/i915: Drop the irqs_disabled() check Maarten Lankhorst
2025-07-15 19:08   ` Rodrigo Vivi [this message]
2025-07-15 15:41 ` [PATCH 3/4] drm/i915/guc: Consider also RCU depth in busy loop Maarten Lankhorst
2025-07-15 15:41 ` [PATCH 4/4] drm/i915: Consider RCU read section as atomic Maarten Lankhorst
2025-07-15 19:08   ` Rodrigo Vivi
2025-07-15 21:22 ` ✗ i915.CI.BAT: failure for CI test the -gt-next patches Patchwork
2025-07-16  9:29 ` ✓ i915.CI.BAT: success for CI test the -gt-next patches. (rev2) Patchwork
2025-07-16 23:23 ` ✗ i915.CI.Full: failure " Patchwork

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=aHanKmYpOt-4XXOv@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=dev@lankhorst.se \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=tvrtko.ursulin@igalia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.