From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <michal.wajdeczko@intel.com>
Subject: Re: [PATCH v4 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API
Date: Wed, 30 Sep 2026 12:18:08 +0530 [thread overview]
Message-ID: <1d249b0f-5d0d-491c-aa34-20b8fa63d886@intel.com> (raw)
In-Reply-To: <20260928092114.1610203-13-dnyaneshwar.bhadane@intel.com>
On 28-09-2026 02:51 pm, 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>
> ---
> drivers/gpu/drm/xe/xe_vram.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vram.c b/drivers/gpu/drm/xe/xe_vram.c
> index fa06c7ae56b1..6c8558042ad4 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");
Message should start with small or capital letter, make it consistency
across all logs.
> return -ENXIO;
> }
>
> @@ -254,8 +256,13 @@ 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,
> + "Tile without any CPU visible VRAM. Aborting.\n");
> + } else {
> + xe_log_err_fatal(xe, VRAM, -ENODEV,
> + "Device without any CPU visible VRAM. Aborting.\n");
> + }
hmm, we can change it like:
xe_log_err_fatal(tile ? tile : xe, VRAM, -ENODEV, "%s without any CPU visible VRAM. Aborting.\n",
tile ? "Tile" : "Device");
right?
> return -ENODEV;
> }
>
> @@ -320,7 +327,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;
>
> @@ -342,8 +349,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);
next prev parent reply other threads:[~2026-09-30 6:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:21 [PATCH v4 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-09-29 5:15 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-09-29 5:25 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-09-29 5:34 ` Mallesh, Koujalagi
2026-10-01 9:50 ` Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-09-28 9:30 ` sashiko-bot
2026-09-28 12:32 ` Bhadane, Dnyaneshwar
2026-09-29 5:40 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-09-28 9:31 ` sashiko-bot
2026-09-28 12:35 ` Bhadane, Dnyaneshwar
2026-09-28 9:21 ` [PATCH v4 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-09-29 5:58 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-09-29 6:34 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-09-28 9:36 ` sashiko-bot
2026-09-29 4:51 ` Dnyaneshwar Bhadane
2026-09-29 4:52 ` Dnyaneshwar Bhadane
2026-09-30 8:36 ` Mallesh, Koujalagi
2026-09-28 9:21 ` [PATCH v4 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-09-28 9:21 ` [PATCH v4 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-09-28 9:33 ` sashiko-bot
2026-09-30 6:48 ` Mallesh, Koujalagi [this message]
2026-10-07 20:20 ` Dnyaneshwar Bhadane
2026-09-28 16:14 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to structured xe_log API (rev4) Patchwork
2026-09-28 16:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-28 20:42 ` ✗ 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=1d249b0f-5d0d-491c-aa34-20b8fa63d886@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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