Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH v2 6/8] drm/i915: Drop the irqs_disabled() check
Date: Wed, 19 Jun 2024 11:28:41 +0100	[thread overview]
Message-ID: <773519fb-3dd9-4c80-87f5-da2cd075deb5@ursulin.net> (raw)
In-Reply-To: <20240613102818.4056866-7-bigeasy@linutronix.de>


On 13/06/2024 11:20, Sebastian Andrzej Siewior wrote:
> 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>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>   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 519e096c607cd..466b5ee8ed6d2 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);
>   
>   	/*

Maarten can you r-b since it seems this one originated from your 
testing? Otherwise:

Acked-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>

Regards,

Tvrtko

  reply	other threads:[~2024-06-19 10:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 10:20 [PATCH v2 0/8] drm/i915: PREEMPT_RT related fixups Sebastian Andrzej Siewior
2024-06-13 10:20 ` [PATCH v2 1/8] drm/i915: Use preempt_disable/enable_rt() where recommended Sebastian Andrzej Siewior
2024-06-13 10:20 ` [PATCH v2 2/8] drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates Sebastian Andrzej Siewior
2024-06-13 10:20 ` [PATCH v2 3/8] drm/i915: Don't check for atomic context on PREEMPT_RT Sebastian Andrzej Siewior
2024-06-14  8:32   ` Tvrtko Ursulin
2024-06-14 11:05     ` Sebastian Andrzej Siewior
2024-06-14 12:19       ` Tvrtko Ursulin
2024-06-17 10:07         ` Sebastian Andrzej Siewior
2024-06-18  9:00           ` Tvrtko Ursulin
2024-06-18 12:54             ` Sebastian Andrzej Siewior
2024-06-19 10:26               ` Tvrtko Ursulin
2024-06-13 10:20 ` [PATCH v2 4/8] drm/i915: Disable tracing points " Sebastian Andrzej Siewior
2024-06-19 10:27   ` Tvrtko Ursulin
2024-06-13 10:20 ` [PATCH v2 5/8] drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() + spin_lock() Sebastian Andrzej Siewior
2024-06-13 10:20 ` [PATCH v2 6/8] drm/i915: Drop the irqs_disabled() check Sebastian Andrzej Siewior
2024-06-19 10:28   ` Tvrtko Ursulin [this message]
2024-06-13 10:20 ` [PATCH v2 7/8] drm/i915/guc: Consider also RCU depth in busy loop Sebastian Andrzej Siewior
2024-06-13 10:20 ` [PATCH v2 8/8] Revert "drm/i915: Depend on !PREEMPT_RT." Sebastian Andrzej Siewior
2024-06-19 10:29   ` Tvrtko Ursulin
2024-06-13 11:52 ` ✓ CI.Patch_applied: success for drm/i915: PREEMPT_RT related fixups. (rev3) Patchwork
2024-06-13 11:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-13 11:53 ` ✓ CI.KUnit: success " Patchwork
2024-06-13 12:05 ` ✓ CI.Build: " Patchwork
2024-06-13 12:07 ` ✗ CI.Hooks: failure " Patchwork
2024-06-13 12:09 ` ✗ CI.checksparse: warning " Patchwork
2024-06-13 12:31 ` ✓ CI.BAT: success " Patchwork
2024-06-13 14:34 ` ✓ CI.FULL: " Patchwork
2024-06-17 10:12 ` ✓ CI.Patch_applied: success for drm/i915: PREEMPT_RT related fixups. (rev4) Patchwork
2024-06-17 10:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-17 10:13 ` ✓ CI.KUnit: success " Patchwork
2024-06-17 10:26 ` ✓ CI.Build: " Patchwork
2024-06-17 10:30 ` ✗ CI.Hooks: failure " Patchwork
2024-06-17 10:32 ` ✗ CI.checksparse: warning " Patchwork
2024-06-17 10:54 ` ✓ CI.BAT: success " Patchwork
2024-06-17 16:35 ` ✓ CI.FULL: " 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=773519fb-3dd9-4c80-87f5-da2cd075deb5@ursulin.net \
    --to=tursulin@ursulin.net \
    --cc=bigeasy@linutronix.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --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