From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Properly handle alloc_guc_id() failure
Date: Tue, 21 May 2024 22:07:40 +0200 [thread overview]
Message-ID: <a429c063-3357-4366-a8ab-ebc604322e5e@linux.intel.com> (raw)
In-Reply-To: <20240521193739.4298-1-niranjana.vishwanathapura@intel.com>
On 5/21/2024 9:37 PM, Niranjana Vishwanathapura wrote:
> Release the submission_state lock if alloc_guc_id() fails.
>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Wow, this goes all the way back. Make sense to add below tags
Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
Cc: <stable@vger.kernel.org> # v6.8+
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index ad2b8067d071..c0b901c5565b 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1304,6 +1304,7 @@ static int guc_exec_queue_init(struct xe_exec_queue *q)
> return 0;
>
> err_entity:
> + mutex_unlock(&guc->submission_state.lock);
> xe_sched_entity_fini(&ge->entity);
> err_sched:
> xe_sched_fini(&ge->sched);
next prev parent reply other threads:[~2024-05-21 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 19:37 [PATCH] drm/xe: Properly handle alloc_guc_id() failure Niranjana Vishwanathapura
2024-05-21 20:06 ` Matthew Brost
2024-05-21 20:07 ` Nirmoy Das [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-21 20:12 Niranjana Vishwanathapura
2024-05-21 20:26 ` Randhawa, Jagmeet
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=a429c063-3357-4366-a8ab-ebc604322e5e@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@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