From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Check result of drmm_mutex_init()
Date: Wed, 10 Apr 2024 09:58:45 +0530 [thread overview]
Message-ID: <c420106e-d516-4317-9ab6-462d9d72bd61@intel.com> (raw)
In-Reply-To: <yzab3rps47j7t5o7cbi22yek7xzfmne2c6fa7bhgmsnedtpt5u@b2aje4vank6e>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
On 09-04-2024 23:31, Lucas De Marchi wrote:
> On Tue, Apr 09, 2024 at 05:31:32PM +0200, Michal Wajdeczko wrote:
>> Although it's unlikely that drmm_mutex_init() will fail during
>> driver initialization, however we shouldn't ignore this case.
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> there was already a patch pending for this, but got stuck because it was
> trying to do something similar for all the display mutexes, that
> shouldn't be there in the first place. Not sure if we take that one with
> conflict resolved or this.
If the patch mentioned is
https://patchwork.freedesktop.org/series/131300/, it does not resolve
the mutex mentioned above.
>
>> ---
>> drivers/gpu/drm/xe/xe_device.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_device.c
>> b/drivers/gpu/drm/xe/xe_device.c
>> index 9083f5e02dd9..ba3643906d9e 100644
>> --- a/drivers/gpu/drm/xe/xe_device.c
>> +++ b/drivers/gpu/drm/xe/xe_device.c
>> @@ -273,7 +273,9 @@ struct xe_device *xe_device_create(struct pci_dev
>> *pdev,
>>
>> init_waitqueue_head(&xe->ufence_wq);
>>
>> - drmm_mutex_init(&xe->drm, &xe->usm.lock);
>> + err = drmm_mutex_init(&xe->drm, &xe->usm.lock);
>> + if (err)
>> + goto err;
>
> blank line missing
>
> Lucas De Marchi
>
>> xa_init_flags(&xe->usm.asid_to_vm, XA_FLAGS_ALLOC);
>>
>> if (IS_ENABLED(CONFIG_DRM_XE_DEBUG)) {
>> --
>> 2.43.0
>>
[-- Attachment #2: Type: text/html, Size: 7585 bytes --]
next prev parent reply other threads:[~2024-04-10 4:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 15:31 [PATCH] drm/xe: Check result of drmm_mutex_init() Michal Wajdeczko
2024-04-09 15:37 ` Ghimiray, Himal Prasad
2024-04-09 15:39 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-09 15:39 ` ✓ CI.checkpatch: " Patchwork
2024-04-09 15:40 ` ✓ CI.KUnit: " Patchwork
2024-04-09 15:52 ` ✓ CI.Build: " Patchwork
2024-04-09 15:56 ` ✓ CI.Hooks: " Patchwork
2024-04-09 15:58 ` ✓ CI.checksparse: " Patchwork
2024-04-09 16:20 ` ✓ CI.BAT: " Patchwork
2024-04-09 17:22 ` ✗ CI.FULL: failure " Patchwork
2024-04-09 18:01 ` [PATCH] " Lucas De Marchi
2024-04-10 4:28 ` Ghimiray, Himal Prasad [this message]
2024-04-10 13:50 ` Lucas De Marchi
2024-04-24 22:38 ` Lucas De Marchi
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=c420106e-d516-4317-9ab6-462d9d72bd61@intel.com \
--to=himal.prasad.ghimiray@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