From: Maciej Patelczyk <maciej.patelczyk@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Vishwanathapura,
Niranjana" <niranjana.vishwanathapura@intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH] drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init()
Date: Fri, 30 May 2025 16:22:56 +0200 [thread overview]
Message-ID: <1b0ec584-8eaa-468a-8d97-e2a11add3e57@intel.com> (raw)
In-Reply-To: <CH0PR11MB5444F39447DA84B2B22D4DD9E561A@CH0PR11MB5444.namprd11.prod.outlook.com>
On 30.05.2025 16:07, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Maciej Patelczyk
> Sent: Friday, May 30, 2025 1:49 AM
> To: intel-xe@lists.freedesktop.org
> Cc: Vishwanathapura, Niranjana <niranjana.vishwanathapura@intel.com>; Brost, Matthew <matthew.brost@intel.com>; maarten.lankhorst@linux.intel.com; Patelczyk, Maciej <maciej.patelczyk@intel.com>
> Subject: [PATCH] drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init()
>> There is unmatched xe_vm_unlock() in the __xe_exec_queue_init().
>> Leftover from fbeaad071a98 ("drm/xe: Create LRC BO without VM")
> Good catch!
> There's a checkpatch warning asking for this commit message to be
> updated to something like:
> """
> There is an unmatched xe_vm_unlock() in the __xe_exec_queue_init()
> function, leftover from
> commit fbeaad071a98 ("drm/xe: Create LRC BO without VM").
> Remove it.
> """
> But besides the checkpatch issue:
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> -Jonathan Cavitt
Thanks!
Maciej
>> Fixes: fbeaad071a98 ("drm/xe: Create LRC BO without VM")
>> Signed-off-by: Maciej Patelczyk <maciej.patelczyk@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_exec_queue.c | 6 +-----
>> 1 file changed, 1 insertion(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
>> index 32c6923df7c3..fee22358cc09 100644
>> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
>> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
>> @@ -114,7 +114,6 @@ static struct xe_exec_queue *__xe_exec_queue_alloc(struct xe_device *xe,
>>
>> static int __xe_exec_queue_init(struct xe_exec_queue *q)
>> {
>> - struct xe_vm *vm = q->vm;
>> int i, err;
>> u32 flags = 0;
>>
>> @@ -136,7 +135,7 @@ static int __xe_exec_queue_init(struct xe_exec_queue *q)
>> q->lrc[i] = xe_lrc_create(q->hwe, q->vm, SZ_16K, q->msix_vec, flags);
>> if (IS_ERR(q->lrc[i])) {
>> err = PTR_ERR(q->lrc[i]);
>> - goto err_unlock;
>> + goto err_lrc;
>> }
>> }
>>
>> @@ -146,9 +145,6 @@ static int __xe_exec_queue_init(struct xe_exec_queue *q)
>>
>> return 0;
>>
>> -err_unlock:
>> - if (vm)
>> - xe_vm_unlock(vm);
>> err_lrc:
>> for (i = i - 1; i >= 0; --i)
>> xe_lrc_put(q->lrc[i]);
>> --
>> 2.35.0
>>
>>
next prev parent reply other threads:[~2025-05-30 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 8:48 [PATCH] drm/xe: remove unmatched xe_vm_unlock() from __xe_exec_queue_init() Maciej Patelczyk
2025-05-30 10:22 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-30 10:22 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-30 10:23 ` ✓ CI.KUnit: success " Patchwork
2025-05-30 10:33 ` ✓ CI.Build: " Patchwork
2025-05-30 10:36 ` ✓ CI.Hooks: " Patchwork
2025-05-30 10:37 ` ✓ CI.checksparse: " Patchwork
2025-05-30 11:08 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-30 14:07 ` [PATCH] " Cavitt, Jonathan
2025-05-30 14:22 ` Maciej Patelczyk [this message]
2025-05-31 18:11 ` ✗ Xe.CI.Full: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 13:56 [PATCH] " Maciej Patelczyk
2025-05-30 21:02 ` 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=1b0ec584-8eaa-468a-8d97-e2a11add3e57@intel.com \
--to=maciej.patelczyk@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--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