Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v6 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API
Date: Mon, 12 Oct 2026 14:38:01 +0530	[thread overview]
Message-ID: <82884f13-e5de-4ab8-8723-beecbf764965@intel.com> (raw)
In-Reply-To: <20261012051823.2201360-13-dnyaneshwar.bhadane@intel.com>


On 12-10-2026 10:48 am, Dnyaneshwar Bhadane wrote:
> Replace drm_err()/drm_info() with xe_log_err_fatal()/xe_log_info()
> using the VRAM component tag. The "no CPU visible VRAM" error uses
> tile or device as the log location depending on the caller context.
>
> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>
> ---
> v2:
>   - Update the ternary condition (Mallesh)
> ---
>   drivers/gpu/drm/xe/xe_vram.c | 38 ++++++++++++++++++++++--------------
>   1 file changed, 23 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vram.c b/drivers/gpu/drm/xe/xe_vram.c
> index 73aef047eb38..772704dfe12f 100644
> --- a/drivers/gpu/drm/xe/xe_vram.c
> +++ b/drivers/gpu/drm/xe/xe_vram.c
> @@ -17,6 +17,7 @@
>   #include "xe_device.h"
>   #include "xe_force_wake.h"
>   #include "xe_gt_mcr.h"
> +#include "xe_log.h"
>   #include "xe_map.h"
>   #include "xe_migrate.h"
>   #include "xe_mmio.h"
> @@ -46,7 +47,8 @@ static int determine_lmem_bar_size(struct xe_device *xe, struct xe_vram_region *
>   	struct pci_dev *pdev = to_pci_dev(xe->drm.dev);
>   
>   	if (!resource_is_valid(pdev, LMEM_BAR)) {
> -		drm_err(&xe->drm, "pci resource is not valid\n");
> +		xe_log_err_fatal(xe, VRAM, -ENXIO,
> +				 "PCI resource is not valid\n");
>   		return -ENXIO;
>   	}
>   
> @@ -227,17 +229,16 @@ struct xe_vram_region *xe_vram_region_alloc(struct xe_device *xe, u8 id, u32 pla
>   
>   static void print_vram_region_info(struct xe_device *xe, struct xe_vram_region *vram)
>   {
> -	struct drm_device *drm = &xe->drm;
>   
>   	if (vram->io_size < vram->usable_size)
> -		drm_info(drm, "Small BAR device\n");
> -
> -	drm_info(drm,
> -		 "VRAM[%u]: Actual physical size %pa, usable size exclude stolen %pa, CPU accessible size %pa\n",
> -		 vram->id, &vram->actual_physical_size, &vram->usable_size, &vram->io_size);
> -	drm_info(drm, "VRAM[%u]: DPA range: [%pa-%llx], io range: [%pa-%llx]\n",
> -		 vram->id, &vram->dpa_base, vram->dpa_base + (u64)vram->actual_physical_size,
> -		 &vram->io_start, vram->io_start + (u64)vram->io_size);
> +		xe_log_info(xe, VRAM, "Small BAR device\n");
> +
> +	xe_log_info(xe, VRAM,
> +		    "[%u]: Actual physical size %pa, usable size exclude stolen %pa, CPU accessible size %pa\n",
> +		    vram->id, &vram->actual_physical_size, &vram->usable_size, &vram->io_size);
> +	xe_log_info(xe, VRAM, "[%u]: DPA range: [%pa-%llx], io range: [%pa-%llx]\n",
> +		    vram->id, &vram->dpa_base, vram->dpa_base + (u64)vram->actual_physical_size,
> +		    &vram->io_start, vram->io_start + (u64)vram->io_size);
>   }
>   
>   static int vram_region_init(struct xe_device *xe, struct xe_vram_region *vram,
> @@ -255,8 +256,14 @@ static int vram_region_init(struct xe_device *xe, struct xe_vram_region *vram,
>   	vram->io_size = min_t(u64, usable_size, remain_io_size);
>   
>   	if (!vram->io_size) {
> -		drm_err(&xe->drm, "%s without any CPU visible VRAM. Aborting.\n",
> -			tile ? "Tile" : "Device");
> +		if (tile) {
> +			xe_log_err_fatal(tile, VRAM, -ENODEV,
> +					 "without any CPU visible VRAM. Aborting.\n");

Rephrase the message, out put looks like:

<3> xe 0000:03:00.0: [drm] *ERROR* SIGID=108 FATAL (-ENODEV) Tile0: 
VRAM: without any CPU visible VRAM. Aborting.

> +		} else {
> +			xe_log_err_fatal(xe, VRAM, -ENODEV,
> +					 "without any CPU visible VRAM. Aborting.\n");
Device is required right? and rephrase the message.
> +		}
> +
>   		return -ENODEV;
>   	}
>   
> @@ -321,7 +328,7 @@ int xe_vram_probe(struct xe_device *xe)
>   	err = determine_lmem_bar_size(xe, &lmem_bar);
>   	if (err)
>   		return err;
> -	drm_info(&xe->drm, "VISIBLE VRAM: %pa, %pa\n", &lmem_bar.io_start, &lmem_bar.io_size);
> +	xe_log_info(xe, VRAM, "VISIBLE VRAM: %pa, %pa\n", &lmem_bar.io_start, &lmem_bar.io_size);
>   
>   	remain_io_size = lmem_bar.io_size;
>   
> @@ -343,8 +350,9 @@ int xe_vram_probe(struct xe_device *xe)
>   			return err;
>   
>   		if (total_size > lmem_bar.io_size) {
> -			drm_info(&xe->drm, "VRAM: %pa is larger than resource %pa\n",
> -				 &total_size, &lmem_bar.io_size);
> +			xe_log_info(xe, VRAM,
> +				    "Total size %pa is larger than resource %pa\n",
> +				    &total_size, &lmem_bar.io_size);
>   		}
>   
>   		remain_io_size -= min_t(u64, tile->mem.vram->actual_physical_size, remain_io_size);

  parent reply	other threads:[~2026-10-12  9:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  5:18 [PATCH v6 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-10-12  5:28   ` sashiko-bot
2026-10-12  5:18 ` [PATCH v6 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-10-12  5:18 ` [PATCH v6 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-10-12  9:01   ` Mallesh, Koujalagi
2026-10-12  5:18 ` [PATCH v6 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12  5:30   ` sashiko-bot
2026-10-12  9:08   ` Mallesh, Koujalagi [this message]
2026-10-12  5:48 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to structured xe_log API (rev6) Patchwork
2026-10-12  6:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-12  7:58 ` ✓ Xe.CI.FULL: " 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=82884f13-e5de-4ab8-8723-beecbf764965@intel.com \
    --to=mallesh.koujalagi@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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