Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>,
	"Auld, Matthew" <matthew.auld@intel.com>,
	"Brost, Matthew" <matthew.brost@intel.com>,
	"Upadhyay, Tejas" <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:22:59 +0200	[thread overview]
Message-ID: <fc9aca26-1f4e-49cb-b11b-cd51e03d493a@intel.com> (raw)
In-Reply-To: <CH0PR11MB5444BB63F191EACB8572EBDBE5432@CH0PR11MB5444.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]


On 10/22/2024 12:28 AM, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Nirmoy Das
> Sent: Monday, October 21, 2024 2:12 PM
> To: intel-xe@lists.freedesktop.org
> Cc: Das, Nirmoy <nirmoy.das@intel.com>; Ghimiray, Himal Prasad <himal.prasad.ghimiray@intel.com>; Auld, Matthew <matthew.auld@intel.com>; Brost, Matthew <matthew.brost@intel.com>; Upadhyay, Tejas <tejas.upadhyay@intel.com>
> Subject: [PATCH] drm/xe: Don't restart parallel queues multiple times on GT reset
>> 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>
> This makes sense, though I'd assume we'd want at least one of
> the GuC IDs to restart the exec queue during a GT reset.  Is that
> what exec_queue_enabled helps allow?

Yes exec_queue_enabled() should be false for the 1st one but as Matt pointed out this is racy. So I will resend this with

Matt suggested check.

Regards,

Nirmoy

>
> I won't block on it presently, just was curious if that case was being
> handled, or if we didn't need to worry about it.
>
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> -Jonathan Cavitt
>
>> ---
>>  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;
>> +
>>  		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: 4717 bytes --]

  reply	other threads:[~2024-10-22  7:23 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 [this message]
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
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=fc9aca26-1f4e-49cb-b11b-cd51e03d493a@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --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