From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/xe: Fix xe_assert usage when jobs timeout
Date: Wed, 10 Jan 2024 21:22:21 +0100 [thread overview]
Message-ID: <a807c30a-3a78-47d2-8fa6-c75a3003354b@intel.com> (raw)
In-Reply-To: <20240110014306.1406523-1-matthew.brost@intel.com>
On 10.01.2024 02:43, Matthew Brost wrote:
> Both kernel and vm jobs should not timeout but it is possible if the
> hardware encounters an error. Do not use asserts in the case rather a
> warn as hardware issues should not result in an assert crashing the
> kernel.
what kind of crash was it ?
xe_assert() uses drm_WARN() which in turn uses WARN()
and XE_WARN_ON() at the end also translates to WARN()
is it due use of xe or xe->drm in xe_assert()?
but then drm_notice() below will also crash
>
> Fixes: c73acc1eeba5 ("drm/xe: Use Xe assert macros instead of XE_WARN_ON macro")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 54ffcfcdd41f..751b822c23da 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -928,8 +928,8 @@ guc_exec_queue_timedout_job(struct drm_sched_job *drm_job)
> int i = 0;
>
> if (!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &job->fence->flags)) {
> - xe_assert(xe, !(q->flags & EXEC_QUEUE_FLAG_KERNEL));
> - xe_assert(xe, !(q->flags & EXEC_QUEUE_FLAG_VM && !exec_queue_killed(q)));
> + XE_WARN_ON(q->flags & EXEC_QUEUE_FLAG_KERNEL);
> + XE_WARN_ON(q->flags & EXEC_QUEUE_FLAG_VM && !exec_queue_killed(q));
>
> drm_notice(&xe->drm, "Timedout job: seqno=%u, guc_id=%d, flags=0x%lx",
> xe_sched_job_seqno(job), q->guc->id, q->flags);
prev parent reply other threads:[~2024-01-10 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 1:43 [PATCH] drm/xe: Fix xe_assert usage when jobs timeout Matthew Brost
2024-01-10 4:17 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-10 4:17 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-10 4:18 ` ✓ CI.KUnit: success " Patchwork
2024-01-10 4:26 ` ✓ CI.Build: " Patchwork
2024-01-10 4:26 ` ✓ CI.Hooks: " Patchwork
2024-01-10 4:27 ` ✓ CI.checksparse: " Patchwork
2024-01-10 5:02 ` ✓ CI.BAT: " Patchwork
2024-01-10 20:01 ` [PATCH] " Rodrigo Vivi
2024-01-10 20:22 ` Michal Wajdeczko [this message]
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=a807c30a-3a78-47d2-8fa6-c75a3003354b@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@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