[PATCH] drm/amdkfd: Use pr_debug to print the message of reaching event limit

Felix Kuehling felix.kuehling at amd.com
Mon Mar 9 19:30:46 UTC 2020


On 2020-03-09 14:25, Yong Zhao wrote:
> People are inclined to think of the previous pr_warn message as an
> error, so use pre_debug instead.
>
> Change-Id: I3ac565a2bd3b8d57345812104c872183898d237f
> Signed-off-by: Yong Zhao <Yong.Zhao at amd.com>

Reviewed-by: Felix Kuehling <Felix.Kuehling at amd.com>

Thanks,
   Felix

> ---
>   drivers/gpu/drm/amd/amdkfd/kfd_events.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_events.c b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> index 1f8365575b12..15476fca8fa6 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_events.c
> @@ -187,7 +187,7 @@ static int create_signal_event(struct file *devkfd,
>   	if (p->signal_mapped_size &&
>   	    p->signal_event_count == p->signal_mapped_size / 8) {
>   		if (!p->signal_event_limit_reached) {
> -			pr_warn("Signal event wasn't created because limit was reached\n");
> +			pr_debug("Signal event wasn't created because limit was reached\n");
>   			p->signal_event_limit_reached = true;
>   		}
>   		return -ENOSPC;


More information about the amd-gfx mailing list