Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: Matthew Auld <matthew.auld@intel.com>,
	Nirmoy Das <nirmoy.das@linux.intel.com>,
	Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Use drm_sched_priority enum instead of 0
Date: Fri, 12 Apr 2024 17:08:46 +0200	[thread overview]
Message-ID: <f51d839a-3245-4665-9ead-379b385bf278@intel.com> (raw)
In-Reply-To: <8e7025c2-033b-4be0-a32e-f97aed327430@intel.com>


On 4/12/2024 2:48 PM, Matthew Auld wrote:
> On 12/04/2024 13:03, Nirmoy Das wrote:
>> Hi Matt,
>>
>>
>> Shouldn't this be DRM_SCHED_PRIORITY_NORMAL ?
>
> Looks like this was already sent: 
> https://lore.kernel.org/intel-xe/ZgJhpTlz6OfqiaQg@DUT025-TGLU.fm.intel.com/
Ah I missed it. This need to be documented so someone else doesn't 
stumble upon again.
>
>>
>> Regards,
>>
>> Nirmoy
>>
>> On 4/12/2024 1:34 PM, Nirmoy Das wrote:
>>> Use enum drm_sched_priority, DRM_SCHED_PRIORITY_KERNEL
>>> instead of 0.
>>>
>>> Cc: Matthew Auld<matthew.auld@intel.com>
>>> Cc: Matthew Brost<matthew.brost@intel.com>
>>> Signed-off-by: Nirmoy Das<nirmoy.das@intel.com>
>>> ---
>>>   drivers/gpu/drm/xe/xe_execlist.c      | 3 ++-
>>>   drivers/gpu/drm/xe/xe_gpu_scheduler.h | 2 +-
>>>   2 files changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/xe/xe_execlist.c 
>>> b/drivers/gpu/drm/xe/xe_execlist.c
>>> index dece2785933c..a8c83b36289f 100644
>>> --- a/drivers/gpu/drm/xe/xe_execlist.c
>>> +++ b/drivers/gpu/drm/xe/xe_execlist.c
>>> @@ -341,7 +341,8 @@ static int execlist_exec_queue_init(struct 
>>> xe_exec_queue *q)
>>>           goto err_free;
>>>         sched = &exl->sched;
>>> -    err = drm_sched_entity_init(&exl->entity, 0, &sched, 1, NULL);
>>> +    err = drm_sched_entity_init(&exl->entity, 
>>> DRM_SCHED_PRIORITY_KERNEL,
>>> +                    &sched, 1, NULL);
>>>       if (err)
>>>           goto err_sched;
>>>   diff --git a/drivers/gpu/drm/xe/xe_gpu_scheduler.h 
>>> b/drivers/gpu/drm/xe/xe_gpu_scheduler.h
>>> index 10c6bb9c9386..1f712f4fc76a 100644
>>> --- a/drivers/gpu/drm/xe/xe_gpu_scheduler.h
>>> +++ b/drivers/gpu/drm/xe/xe_gpu_scheduler.h
>>> @@ -63,7 +63,7 @@ static inline int
>>>   xe_sched_entity_init(struct xe_sched_entity *entity,
>>>                struct xe_gpu_scheduler *sched)
>>>   {
>>> -    return drm_sched_entity_init(entity, 0,
>>> +    return drm_sched_entity_init(entity, DRM_SCHED_PRIORITY_KERNEL,
>>>                        (struct drm_gpu_scheduler **)&sched,
>>>                        1, NULL);
>>>   }

  reply	other threads:[~2024-04-12 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 11:34 [PATCH] drm/xe: Use drm_sched_priority enum instead of 0 Nirmoy Das
2024-04-12 12:03 ` Nirmoy Das
2024-04-12 12:48   ` Matthew Auld
2024-04-12 15:08     ` Nirmoy Das [this message]
2024-04-15 10:11 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-15 10:11 ` ✓ CI.checkpatch: " Patchwork
2024-04-15 10:12 ` ✓ CI.KUnit: " Patchwork
2024-04-15 10:24 ` ✓ CI.Build: " Patchwork
2024-04-15 10:26 ` ✓ CI.Hooks: " Patchwork
2024-04-15 10:28 ` ✓ CI.checksparse: " Patchwork
2024-04-15 10:56 ` ✓ CI.BAT: " Patchwork
2024-04-15 15:03 ` ✓ CI.FULL: " 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=f51d839a-3245-4665-9ead-379b385bf278@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=nirmoy.das@linux.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