Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH v4 2/2] drm/xe: Upgrade job timeout message to warn
Date: Fri, 25 Oct 2024 16:24:41 -0700	[thread overview]
Message-ID: <dbcc0ff8-fd93-4cee-aa5d-c6a023768626@intel.com> (raw)
In-Reply-To: <20241025214330.2010521-3-matthew.brost@intel.com>

On 10/25/2024 14:43, Matthew Brost wrote:
> Ensure job timeout message shows up on distro configs for user bug
> reports. Change job timeout message from notice to warn.
I don't think you are allowed to do this. Job timeouts occur when the 
user submits bad batch buffers. They are expected error handling for 
untrusted user programs. As such, they should not generate warnings or 
errors. Same as passing dodgy data into an IOCTL should not generate a 
warning but just return EINVAL or similar.

John.

>
> Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> Cc: stable@vger.kernel.org
> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_guc_submit.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 7afcc243037c..067cf2bfac1e 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1154,9 +1154,9 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
>   		process_name = q->vm->xef->process_name;
>   		pid = q->vm->xef->pid;
>   	}
> -	xe_gt_notice(guc_to_gt(guc), "Timedout job: seqno=%u, lrc_seqno=%u, guc_id=%d, flags=0x%lx in %s [%d]",
> -		     xe_sched_job_seqno(job), xe_sched_job_lrc_seqno(job),
> -		     q->guc->id, q->flags, process_name, pid);
> +	xe_gt_warn(guc_to_gt(guc), "Timedout job: seqno=%u, lrc_seqno=%u, guc_id=%d, flags=0x%lx in %s [%d]",
> +		   xe_sched_job_seqno(job), xe_sched_job_lrc_seqno(job),
> +		   q->guc->id, q->flags, process_name, pid);
>   
>   	trace_xe_sched_job_timedout(job);
>   


  reply	other threads:[~2024-10-25 23:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 21:43 [PATCH v4 0/2] Tweak job timeout debug messages Matthew Brost
2024-10-25 21:43 ` [PATCH v4 1/2] drm/xe: Don't short circuit TDR on jobs not started Matthew Brost
2024-10-31  5:20   ` Lucas De Marchi
2024-10-25 21:43 ` [PATCH v4 2/2] drm/xe: Upgrade job timeout message to warn Matthew Brost
2024-10-25 23:24   ` John Harrison [this message]
2024-10-29 17:45     ` Matthew Brost
2024-10-25 22:32 ` ✓ CI.Patch_applied: success for Tweak job timeout debug messages Patchwork
2024-10-25 22:32 ` ✓ CI.checkpatch: " Patchwork
2024-10-25 22:33 ` ✓ CI.KUnit: " Patchwork
2024-10-25 22:45 ` ✓ CI.Build: " Patchwork
2024-10-25 22:47 ` ✓ CI.Hooks: " Patchwork
2024-10-25 22:48 ` ✓ CI.checksparse: " Patchwork
2024-10-25 23:12 ` ✓ CI.BAT: " Patchwork
2024-10-27 14:34 ` ✗ CI.FULL: failure " 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=dbcc0ff8-fd93-4cee-aa5d-c6a023768626@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=paulo.r.zanoni@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