[PATCH 1/1] drm/xe: Use enum instead of hard coding
Rodrigo Vivi
rodrigo.vivi at intel.com
Thu Mar 21 19:41:14 UTC 2024
On Thu, Mar 21, 2024 at 04:09:28PM +0530, Himal Prasad Ghimiray wrote:
> Use DRM_SCHED_PRIORITY_KERNEL instead of hardcoded value 0.
>
> Cc: Matthew Brost <matthew.brost at intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray at intel.com>
as I told you offline, with the xe_execlist also taken care of:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
> ---
> Coverity Reports "Parse warning (PW.MIXED_ENUM_TYPE)
> 1. mixed_enum_type enumerated type mixed with another type"
>
> drivers/gpu/drm/xe/xe_gpu_scheduler.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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);
> }
> --
> 2.25.1
>
More information about the Intel-xe
mailing list