From: sashiko-bot@kernel.org
To: "Umesh Nerlige Ramappa" <umesh.nerlige.ramappa@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v5 4/7] drm/xe/oa: Skip OA HW teardown on a wedged device
Date: Tue, 10 Nov 2026 19:17:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-207649@kernel.org> (raw)
In-Reply-To: <20261110190052.3514226-13-umesh.nerlige.ramappa@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] drm/xe/oa: build failure from non-existent xe_wedge.h and
xe_wedged()
--
commit cfe215fb928c6338b6dd8582d19a4f894fb6bd7d
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
drm/xe/oa: Skip OA HW teardown on a wedged device
This commit skips OA stream disabling and hardware teardown when destroying
an OA stream on a wedged device, and ensures the poll timer is unconditionally
canceled in xe_oa_stream_destroy().
> diff --git a/drivers/gpu/drm/xe/xe_oa.c b/drivers/gpu/drm/xe/xe_oa.c
> index df9a3ea0875d1..6383a2e036ab0 100644
> --- a/drivers/gpu/drm/xe/xe_oa.c
> +++ b/drivers/gpu/drm/xe/xe_oa.c
> @@ -43,6 +43,7 @@
> #include "xe_sriov.h"
> #include "xe_sync.h"
> #include "xe_wa.h"
> +#include "xe_wedge.h"
[ ... ]
> @@ -905,7 +911,12 @@ static void xe_oa_stream_destroy(struct xe_oa_stream *stream)
>
> mutex_destroy(&stream->stream_lock);
>
> - xe_oa_stream_hw_teardown(stream);
> + /* The poll timer may still be armed if the OA disable was skipped */
> + hrtimer_cancel(&stream->poll_check_timer);
> +
> + if (!xe_wedged(stream->oa->xe))
> + xe_oa_stream_hw_teardown(stream);
> +
> xe_oa_free_oa_buffer(stream);
> xe_oa_stream_free_resources(stream);
> }
> @@ -1704,7 +1715,8 @@ static void xe_oa_destroy_locked(struct xe_oa_stream *stream)
> {
> xe_pm_runtime_get(gt_to_xe(stream->gt));
>
> - if (stream->enabled)
> + /* A wedged device may be unresponsive, skip HW access */
> + if (stream->enabled && !xe_wedged(gt_to_xe(stream->gt)))
> xe_oa_disable_locked(stream);
[Severity: High]
Does this break the build? Neither xe_wedge.h nor xe_wedged() exists in the
tree. The helper for checking whether an xe_device is wedged is
xe_device_wedged() in drivers/gpu/drm/xe/xe_device.h, which xe_oa.c already
includes.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110190052.3514226-9-umesh.nerlige.ramappa@intel.com?part=4
next prev parent reply other threads:[~2026-11-10 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 19:00 [PATCH v5 0/7] Cleanup OA stream on PCI unbind/remove Umesh Nerlige Ramappa
2026-11-10 19:00 ` [PATCH v5 1/7] drm/xe/oa: Use the drm device address_space for the OA stream fd Umesh Nerlige Ramappa
2026-11-10 19:00 ` [PATCH v5 2/7] drm/xe/oa: Split OA stream destroy into HW teardown and resource release Umesh Nerlige Ramappa
2026-11-10 19:00 ` [PATCH v5 3/7] drm/xe/oa: Take the runtime PM reference in xe_oa_destroy_locked() Umesh Nerlige Ramappa
2026-11-10 19:00 ` [PATCH v5 4/7] drm/xe/oa: Skip OA HW teardown on a wedged device Umesh Nerlige Ramappa
2026-11-10 19:17 ` sashiko-bot [this message]
2026-11-10 19:00 ` [PATCH v5 5/7] drm/xe/oa: Wait for in-flight OA batches before stream HW teardown Umesh Nerlige Ramappa
2026-11-10 19:25 ` sashiko-bot
2026-11-10 19:00 ` [PATCH v5 6/7] drm/xe: Reject vm_ops->access on BO mappings of an unplugged device Umesh Nerlige Ramappa
2026-11-10 19:26 ` sashiko-bot
2026-11-10 19:01 ` [PATCH v5 7/7] drm/xe/oa: Quiesce OA streams on driver unbind and PCI reset Umesh Nerlige Ramappa
2026-11-10 19:38 ` sashiko-bot
2026-11-10 20:05 ` ✓ CI.KUnit: success for Cleanup OA stream on PCI unbind/remove (rev5) Patchwork
2026-11-10 20:49 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-11 0:52 ` ✗ Xe.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=sashiko-outbox-207649@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=umesh.nerlige.ramappa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.