Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	riana.tauro@intel.com
Subject: Re: [PATCH] drm/xe/xe_drm_ras: Enable CONFIG_DRM_RAS
Date: Tue, 18 Aug 2026 09:59:15 +0200	[thread overview]
Message-ID: <aoQQ05RgZxVOeY_U@black.igk.intel.com> (raw)
In-Reply-To: <20260818075454.1508724-2-balasubramani.vivekanandan@intel.com>

On Tue, Aug 18, 2026 at 01:24:55PM +0530, Balasubramani Vivekanandan wrote:
> Xe RAS functionality needs DRM RAS support. Enable it.
> 
> Fixes: b40db12b542f5 ("drm/xe/xe_drm_ras: Add support for XE DRM RAS")
> Signed-off-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> ---
>  drivers/gpu/drm/xe/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> index 4d7dcaff2b915..6c584f918edf2 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -42,6 +42,7 @@ config DRM_XE
>  	select DRM_GPUSVM if !UML
>  	select DRM_GPUVM
>  	select DRM_SCHED
> +	select DRM_RAS

Nack, this was an internal workaround. It's upto the user to decide.

Raag

>  	select MMU_NOTIFIER
>  	select WANT_DEV_COREDUMP
>  	select AUXILIARY_BUS
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2026-08-18  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  7:54 [PATCH] drm/xe/xe_drm_ras: Enable CONFIG_DRM_RAS Balasubramani Vivekanandan
2026-08-18  7:52 ` ✗ CI.KUnit: failure for " Patchwork
2026-08-18  7:53 ` [PATCH] " sashiko-bot
2026-08-18  7:59 ` Raag Jadav [this message]
2026-08-18  8:18   ` Tauro, Riana
2026-08-18 13:44     ` Rodrigo Vivi

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=aoQQ05RgZxVOeY_U@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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