From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: Fix locking in CT fast path
Date: Tue, 21 Mar 2023 13:25:51 +0100 [thread overview]
Message-ID: <f85589d5-b3ac-89c8-6a24-9c51d10d3710@linux.intel.com> (raw)
In-Reply-To: <20230317002221.211065-1-matthew.brost@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2646 bytes --]
Hey,
I'm afraid this is not allowed, you can't take a mutex in an irq handler, not even a trylock.
From Documentation/locking/mutex-design.rst:
The mutex subsystem checks and enforces the following rules:
...
- Mutexes may not be used in hardware or software interrupt
contexts such as tasklets and timers.
Lockdep will likely still splat too as a result.
Cheers,
~Maarten
On 2023-03-17 01:22, Matthew Brost wrote:
> We can't sleep in the CT fast but need to ensure we can access VRAM. Use
> a trylock + reference counter check to ensure safe access to VRAM, if
> either check fails, fall back to slow path.
>
> VLK-45296
>
> Signed-off-by: Matthew Brost<matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device.h | 9 ++++++++-
> drivers/gpu/drm/xe/xe_guc_ct.c | 11 ++++++++++-
> 2 files changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device.h b/drivers/gpu/drm/xe/xe_device.h
> index 25c5087f5aad..0cc4f52098a1 100644
> --- a/drivers/gpu/drm/xe/xe_device.h
> +++ b/drivers/gpu/drm/xe/xe_device.h
> @@ -95,12 +95,19 @@ static inline void xe_device_assert_mem_access(struct xe_device *xe)
> XE_WARN_ON(!xe->mem_access.ref);
> }
>
> +static inline bool __xe_device_mem_access_ongoing(struct xe_device *xe)
> +{
> + lockdep_assert_held(&xe->mem_access.lock);
> +
> + return xe->mem_access.ref;
> +}
> +
> static inline bool xe_device_mem_access_ongoing(struct xe_device *xe)
> {
> bool ret;
>
> mutex_lock(&xe->mem_access.lock);
> - ret = xe->mem_access.ref;
> + ret = __xe_device_mem_access_ongoing(xe);
> mutex_unlock(&xe->mem_access.lock);
>
> return ret;
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index e5ed9022a0a2..bba0ef21c9e5 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -1030,9 +1030,15 @@ void xe_guc_ct_fast_path(struct xe_guc_ct *ct)
> struct xe_device *xe = ct_to_xe(ct);
> int len;
>
> - if (!xe_device_in_fault_mode(xe) || !xe_device_mem_access_ongoing(xe))
> + if (!xe_device_in_fault_mode(xe))
> return;
>
> + if (!mutex_trylock(&xe->mem_access.lock))
> + return;
> +
> + if (!__xe_device_mem_access_ongoing(xe))
> + goto unlock;
> +
> spin_lock(&ct->fast_lock);
> do {
> len = g2h_read(ct, ct->fast_msg, true);
> @@ -1040,6 +1046,9 @@ void xe_guc_ct_fast_path(struct xe_guc_ct *ct)
> g2h_fast_path(ct, ct->fast_msg, len);
> } while (len > 0);
> spin_unlock(&ct->fast_lock);
> +
> +unlock:
> + mutex_unlock(&xe->mem_access.lock);
> }
>
> /* Returns less than zero on error, 0 on done, 1 on more available */
[-- Attachment #2: Type: text/html, Size: 2996 bytes --]
next prev parent reply other threads:[~2023-03-21 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 0:22 [Intel-xe] [PATCH] drm/xe: Fix locking in CT fast path Matthew Brost
2023-03-17 0:24 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-03-17 0:25 ` [Intel-xe] ✗ CI.KUnit: failure " Patchwork
2023-03-21 12:25 ` Maarten Lankhorst [this message]
2023-03-21 14:34 ` [Intel-xe] [PATCH] " Matthew Brost
2023-03-21 21:14 ` Rodrigo Vivi
2023-03-22 12:18 ` Maarten Lankhorst
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=f85589d5-b3ac-89c8-6a24-9c51d10d3710@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox