From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
<intel-xe@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: <riana.tauro@intel.com>, <matthew.d.roper@intel.com>,
<mallesh.koujalagi@intel.com>
Subject: Re: [PATCH v1] drm/xe/drm_ras: Move has_drm_ras check to drm_ras layer
Date: Mon, 3 Aug 2026 11:03:11 +0200 [thread overview]
Message-ID: <3f8aeb27-ab03-424b-a320-45ad137944dd@intel.com> (raw)
In-Reply-To: <20260803080823.1166925-1-raag.jadav@intel.com>
On 8/3/2026 10:08 AM, Raag Jadav wrote:
> has_drm_ras flag is meant to facilitate drm_ras feature. Move it to the
> correct layer where it belogs.
typo: belongs
>
> Fixes: 63dfab5786ca ("drm/xe/xe_ras: Add drm_ras feature flag")
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_drm_ras.c | 3 +++
> drivers/gpu/drm/xe/xe_ras.c | 3 ---
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_drm_ras.c b/drivers/gpu/drm/xe/xe_drm_ras.c
> index 4afa2ad98300..a23cfb49361b 100644
> --- a/drivers/gpu/drm/xe/xe_drm_ras.c
> +++ b/drivers/gpu/drm/xe/xe_drm_ras.c
> @@ -233,6 +233,9 @@ int xe_drm_ras_init(struct xe_device *xe)
> struct drm_ras_node *node;
> int err;
>
> + if (!xe->info.has_drm_ras)
> + return 0;
> +
> node = drmm_kcalloc(&xe->drm, DRM_XE_RAS_ERR_SEV_MAX, sizeof(*node), GFP_KERNEL);
> if (!node)
> return -ENOMEM;
> diff --git a/drivers/gpu/drm/xe/xe_ras.c b/drivers/gpu/drm/xe/xe_ras.c
> index 28123f08e513..f7af4da8172c 100644
> --- a/drivers/gpu/drm/xe/xe_ras.c
> +++ b/drivers/gpu/drm/xe/xe_ras.c
> @@ -816,9 +816,6 @@ void xe_ras_init(struct xe_device *xe)
> {
> int ret;
>
> - if (!xe->info.has_drm_ras)
> - return;
> -
> xe_drm_ras_init(xe);
btw, shouldn't we handle xe_drm_ras_init() errors here?
hmm, and it looks that xe_ras_init() ignores all errors,
which is kind of against the "all-or-nothing" driver rule
(but this is not as something to fix in this patch)
>
> if (!xe->info.has_sysctrl)
next prev parent reply other threads:[~2026-08-03 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 8:08 [PATCH v1] drm/xe/drm_ras: Move has_drm_ras check to drm_ras layer Raag Jadav
2026-08-03 9:03 ` Michal Wajdeczko [this message]
2026-08-03 9:42 ` Raag Jadav
2026-08-03 12:31 ` ✓ CI.KUnit: success for " Patchwork
2026-08-03 14:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-04 10:23 ` ✓ CI.KUnit: " Patchwork
2026-08-05 5:10 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-08-05 6:23 ` ✓ CI.KUnit: success for drm/xe/drm_ras: Move has_drm_ras check to drm_ras layer (rev2) Patchwork
2026-08-05 7:18 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-08-05 13:42 ` ✓ Xe.CI.FULL: success " Patchwork
2026-08-10 10:34 ` [PATCH v1] drm/xe/drm_ras: Move has_drm_ras check to drm_ras layer Tauro, Riana
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=3f8aeb27-ab03-424b-a320-45ad137944dd@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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