From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: Fix lockdep warning in xe_force_wake calls
Date: Fri, 8 Dec 2023 00:17:46 -0500 [thread overview]
Message-ID: <ZXKm-lm_BbzegovV@intel.com> (raw)
In-Reply-To: <20231206095318.30326-1-aravind.iddamsetty@linux.intel.com>
On Wed, Dec 06, 2023 at 03:23:18PM +0530, Aravind Iddamsetty wrote:
> Use spin_lock_irqsave, spin_unlock_irqrestore
>
> Fix for below:
> [13994.811263] ========================================================
> [13994.811295] WARNING: possible irq lock inversion dependency detected
> [13994.811326] 6.6.0-rc3-xe #2 Tainted: G U
> [13994.811358] --------------------------------------------------------
> [13994.811388] swapper/0/0 just changed the state of lock:
> [13994.811416] ffff895c7e044db8 (&cpuctx_lock){-...}-{2:2}, at:
> __perf_event_read+0xb7/0x3a0
> [13994.811494] but this lock took another, HARDIRQ-unsafe lock in the
> past:
> [13994.811528] (&fw->lock){+.+.}-{2:2}
> [13994.811544]
>
> and interrupts could create inverse lock ordering between
> them.
>
> [13994.811606]
> other info that might help us debug this:
> [13994.811636] Possible interrupt unsafe locking scenario:
>
> [13994.811667] CPU0 CPU1
> [13994.811691] ---- ----
> [13994.811715] lock(&fw->lock);
> [13994.811744] local_irq_disable();
> [13994.811773] lock(&cpuctx_lock);
> [13994.811810] lock(&fw->lock);
> [13994.811846] <Interrupt>
> [13994.811865] lock(&cpuctx_lock);
> [13994.811895]
> *** DEADLOCK ***
>
> v2: Use spin_lock in atomic context and spin_lock_irq in a non atomic
> context (Matthew Brost)
>
> v3: just use spin_lock_irqsave/restore
>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
>
> Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_force_wake.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_force_wake.c b/drivers/gpu/drm/xe/xe_force_wake.c
> index 32d6c4dd2807..9bbe8a5040da 100644
> --- a/drivers/gpu/drm/xe/xe_force_wake.c
> +++ b/drivers/gpu/drm/xe/xe_force_wake.c
> @@ -145,9 +145,10 @@ int xe_force_wake_get(struct xe_force_wake *fw,
> struct xe_gt *gt = fw_to_gt(fw);
> struct xe_force_wake_domain *domain;
> enum xe_force_wake_domains tmp, woken = 0;
> + unsigned long flags;
> int ret, ret2 = 0;
>
> - spin_lock(&fw->lock);
> + spin_lock_irqsave(&fw->lock, flags);
> for_each_fw_domain_masked(domain, domains, fw, tmp) {
> if (!domain->ref++) {
> woken |= BIT(domain->id);
> @@ -162,7 +163,7 @@ int xe_force_wake_get(struct xe_force_wake *fw,
> domain->id, ret);
> }
> fw->awake_domains |= woken;
> - spin_unlock(&fw->lock);
> + spin_unlock_irqrestore(&fw->lock, flags);
>
> return ret2;
> }
> @@ -174,9 +175,10 @@ int xe_force_wake_put(struct xe_force_wake *fw,
> struct xe_gt *gt = fw_to_gt(fw);
> struct xe_force_wake_domain *domain;
> enum xe_force_wake_domains tmp, sleep = 0;
> + unsigned long flags;
> int ret, ret2 = 0;
>
> - spin_lock(&fw->lock);
> + spin_lock_irqsave(&fw->lock, flags);
> for_each_fw_domain_masked(domain, domains, fw, tmp) {
> if (!--domain->ref) {
> sleep |= BIT(domain->id);
> @@ -191,7 +193,7 @@ int xe_force_wake_put(struct xe_force_wake *fw,
> domain->id, ret);
> }
> fw->awake_domains &= ~sleep;
> - spin_unlock(&fw->lock);
> + spin_unlock_irqrestore(&fw->lock, flags);
>
> return ret2;
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-12-08 5:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 9:53 [Intel-xe] [PATCH] drm/xe: Fix lockdep warning in xe_force_wake calls Aravind Iddamsetty
2023-12-06 12:08 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Fix lockdep warning in xe_force_wake calls (rev4) Patchwork
2023-12-06 12:08 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-12-06 12:09 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-12-06 12:17 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-12-06 12:17 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-12-06 12:18 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-12-06 12:56 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-12-08 5:17 ` Rodrigo Vivi [this message]
2023-12-08 5:49 ` [Intel-xe] [PATCH] drm/xe: Fix lockdep warning in xe_force_wake calls Aravind Iddamsetty
-- strict thread matches above, loose matches on Subject: below --
2023-11-24 6:44 Aravind Iddamsetty
2023-11-24 7:19 ` Ville Syrjälä
2023-11-24 8:31 ` Aravind Iddamsetty
2023-11-24 8:37 ` Ville Syrjälä
2023-11-28 8:30 ` Aravind Iddamsetty
2023-12-01 3:37 ` Aravind Iddamsetty
2023-11-10 6:29 Aravind Iddamsetty
2023-11-10 13:17 ` Matthew Brost
2023-11-17 8:48 ` Aravind Iddamsetty
2023-11-20 12:32 ` Matthew Brost
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=ZXKm-lm_BbzegovV@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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