Netdev List
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	netdev@vger.kernel.org, rodrigo.vivi@intel.com,
	riana.tauro@intel.com, dev@lankhorst.se, airlied@gmail.com,
	simona@ffwll.ch, kuba@kernel.org
Subject: Re: [PATCH v2 4/4] drm/xe/hw_error: Use HW_ERR prefix in log
Date: Mon, 1 Jun 2026 14:25:01 +0200	[thread overview]
Message-ID: <ah16Hfwq7goxBm27@black.igk.intel.com> (raw)
In-Reply-To: <65752da7-a23d-4495-9863-541bdd3f7888@intel.com>

On Mon, Jun 01, 2026 at 01:13:12PM +0200, Michal Wajdeczko wrote:
> On 5/23/2026 7:00 AM, Raag Jadav wrote:
> > Hardware errors should be logged with HW_ERR prefix. Make them
> > consistent with existing logs.
> > 
> > Fixes: 01aab7e1c9d4 ("drm/xe/xe_hw_error: Add support for PVC SoC errors")
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_hw_error.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_hw_error.c b/drivers/gpu/drm/xe/xe_hw_error.c
> > index 5135e8e4093f..4b72959b2276 100644
> > --- a/drivers/gpu/drm/xe/xe_hw_error.c
> > +++ b/drivers/gpu/drm/xe/xe_hw_error.c
> > @@ -223,9 +223,9 @@ static void log_hw_error(struct xe_tile *tile, const char *name,
> >  	struct xe_device *xe = tile_to_xe(tile);
> >  
> >  	if (severity == DRM_XE_RAS_ERR_SEV_CORRECTABLE)
> > -		drm_warn(&xe->drm, "%s %s detected\n", name, severity_str);
> > +		drm_warn(&xe->drm, HW_ERR "%s %s detected\n", name, severity_str);
> 
> function is per-tile, so shouldn't we use tile-oriented logs instead?

Agree, but then it needs to be done file-wide which I'll pursue once
the fix lands and propageted.

Raag

> 		xe_tile_warn(tile, HW_ERR ...)
> 
> >  	else
> > -		drm_err_ratelimited(&xe->drm, "%s %s detected\n", name, severity_str);
> > +		drm_err_ratelimited(&xe->drm, HW_ERR "%s %s detected\n", name, severity_str);
> 
> 		xe_tile_err_ratelimited(tile, HW_ERR ...)
> 
> >  }
> >  
> >  static void log_gt_err(struct xe_tile *tile, const char *name, int i, u32 err,
> > @@ -235,10 +235,10 @@ static void log_gt_err(struct xe_tile *tile, const char *name, int i, u32 err,
> >  	struct xe_device *xe = tile_to_xe(tile);
> >  
> >  	if (severity == DRM_XE_RAS_ERR_SEV_CORRECTABLE)
> > -		drm_warn(&xe->drm, "%s %s detected, ERROR_STAT_GT_VECTOR%d:0x%08x\n",
> > +		drm_warn(&xe->drm, HW_ERR "%s %s detected, ERROR_STAT_GT_VECTOR%d:0x%08x\n",
> >  			 name, severity_str, i, err);
> >  	else
> > -		drm_err_ratelimited(&xe->drm, "%s %s detected, ERROR_STAT_GT_VECTOR%d:0x%08x\n",
> > +		drm_err_ratelimited(&xe->drm, HW_ERR "%s %s detected, ERROR_STAT_GT_VECTOR%d:0x%08x\n",
> >  				    name, severity_str, i, err);
> >  }
> >  
> > @@ -255,9 +255,9 @@ static void log_soc_error(struct xe_tile *tile, const char * const *reg_info,
> >  
> >  	if (strcmp(name, "Undefined")) {
> >  		if (severity == DRM_XE_RAS_ERR_SEV_CORRECTABLE)
> > -			drm_warn(&xe->drm, "%s SOC %s detected", name, severity_str);
> > +			drm_warn(&xe->drm, HW_ERR "%s SOC %s detected", name, severity_str);
> >  		else
> > -			drm_err_ratelimited(&xe->drm, "%s SOC %s detected", name, severity_str);
> > +			drm_err_ratelimited(&xe->drm, HW_ERR "%s SOC %s detected", name, severity_str);
> >  		atomic_inc(&info[index].counter);
> >  	}
> >  }
> 

      reply	other threads:[~2026-06-01 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  5:00 [PATCH v2 0/4] DRM RAS Fixes Raag Jadav
2026-05-23  5:00 ` [PATCH v2 1/4] drm/ras: Cancel and free message on get counter failure Raag Jadav
2026-05-25  9:53   ` Tauro, Riana
2026-05-23  5:00 ` [PATCH v2 2/4] drm/xe/drm_ras: Make counter allocation drm managed Raag Jadav
2026-05-23  5:00 ` [PATCH v2 3/4] drm/xe/drm_ras: Add per node cleanup action Raag Jadav
2026-06-01  9:13   ` Tauro, Riana
2026-05-23  5:00 ` [PATCH v2 4/4] drm/xe/hw_error: Use HW_ERR prefix in log Raag Jadav
2026-06-01  9:19   ` Tauro, Riana
2026-06-01 11:13   ` Michal Wajdeczko
2026-06-01 12:25     ` Raag Jadav [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=ah16Hfwq7goxBm27@black.igk.intel.com \
    --to=raag.jadav@intel.com \
    --cc=airlied@gmail.com \
    --cc=dev@lankhorst.se \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kuba@kernel.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    /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