From: Nirmoy Das <nirmoy.das@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
Matthew Auld <matthew.auld@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: Re: [PATCH] drm/xe: Don't restart parallel queues multiple times on GT reset
Date: Tue, 22 Oct 2024 09:35:42 +0200 [thread overview]
Message-ID: <7e7e8ef8-98d5-4fe5-9469-ba3fe047d9d2@intel.com> (raw)
In-Reply-To: <Zxbdm8wpXQ8Iu477@DUT025-TGLU.fm.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]
On 10/22/2024 1:02 AM, Matthew Brost wrote:
> On Mon, Oct 21, 2024 at 11:11:46PM +0200, Nirmoy Das wrote:
>> In case of parallel submissions multiple GuC id will point to the
>> same exec queue and on GT reset such exec queues will get restarted
>> multiple times which is not desirable.
>>
>> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2295
>> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_guc_submit.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
>> index 0b81972ff651..6aeb007eaf06 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
>> @@ -1784,8 +1784,13 @@ int xe_guc_submit_start(struct xe_guc *guc)
>>
>> mutex_lock(&guc->submission_state.lock);
>> atomic_dec(&guc->submission_state.stopped);
>> - xa_for_each(&guc->submission_state.exec_queue_lookup, index, q)
>> + xa_for_each(&guc->submission_state.exec_queue_lookup, index, q) {
>> + /* Skip restarting parallel queues */
>> + if (exec_queue_enabled(q) && xe_exec_queue_is_parallel(q))
>> + continue;
> This doesn't look right as exec_queue_enabled can race here...
Ah right, just realized this happens async with the run_job
>
> I think this should be...
>
> if (q->guc->id != index)
> continue;
This looks much better. I will try it out and resend.
>
> This way we only call guc_exec_queue_start once per queue parallel exec
> queue. Also I think we need to add the same check to xe_guc_submit_stop.
I will resend with updated xe_guc_submit_stop()
thanks,
Nirmoy
> Matt
>
>> +
>> guc_exec_queue_start(q);
>> + }
>> mutex_unlock(&guc->submission_state.lock);
>>
>> wake_up_all(&guc->ct.wq);
>> --
>> 2.46.0
>>
[-- Attachment #2: Type: text/html, Size: 3833 bytes --]
next prev parent reply other threads:[~2024-10-22 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 21:11 [PATCH] drm/xe: Don't restart parallel queues multiple times on GT reset Nirmoy Das
2024-10-21 22:26 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-21 22:26 ` ✓ CI.checkpatch: " Patchwork
2024-10-21 22:27 ` ✓ CI.KUnit: " Patchwork
2024-10-21 22:28 ` [PATCH] " Cavitt, Jonathan
2024-10-22 7:22 ` Nirmoy Das
2024-10-21 22:38 ` ✓ CI.Build: success for " Patchwork
2024-10-21 22:41 ` ✓ CI.Hooks: " Patchwork
2024-10-21 22:42 ` ✓ CI.checksparse: " Patchwork
2024-10-21 23:01 ` ✓ CI.BAT: " Patchwork
2024-10-21 23:02 ` [PATCH] " Matthew Brost
2024-10-22 7:35 ` Nirmoy Das [this message]
2024-10-22 5:40 ` ✗ CI.FULL: failure for " Patchwork
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=7e7e8ef8-98d5-4fe5-9469-ba3fe047d9d2@intel.com \
--to=nirmoy.das@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=tejas.upadhyay@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