From: Matthew Brost <matthew.brost@intel.com>
To: Oak Zeng <oak.zeng@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/2] drm/xe: Improve vram info debug printing
Date: Fri, 11 Aug 2023 18:25:18 +0000 [thread overview]
Message-ID: <ZNZ9Dk16chiys59k@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20230808024501.11669-3-oak.zeng@intel.com>
On Mon, Aug 07, 2023 at 10:45:01PM -0400, Oak Zeng wrote:
> Print both device physical address range and CPU io range
> of vram. Also print vram's actual size, usable size excluding
> stolen memory, and CPU io accessible size.
>
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
> ---
> drivers/gpu/drm/xe/xe_mmio.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_mmio.c b/drivers/gpu/drm/xe/xe_mmio.c
> index 0d0966691eaa..9f249c61ff8e 100644
> --- a/drivers/gpu/drm/xe/xe_mmio.c
> +++ b/drivers/gpu/drm/xe/xe_mmio.c
> @@ -286,12 +286,12 @@ int xe_mmio_probe_vram(struct xe_device *xe)
> tile->mem.vram.usable_size = vram_size;
> tile->mem.vram.mapping = xe->mem.vram.mapping + tile_offset;
>
> - drm_info(&xe->drm, "VRAM[%u, %u]: %pa, %pa\n", id, tile->id,
> - &tile->mem.vram.io_start, &tile->mem.vram.usable_size);
> + drm_info(&xe->drm, "VRAM[%u, %u]: Actual physical size %pa, usable size exclude stolen %pa, CPU accessible size %pa\n", id,
> + tile->id, &tile->mem.vram.actual_physical_size, &tile->mem.vram.usable_size, &tile->mem.vram.io_size);
>
> - if (tile->mem.vram.io_size < tile->mem.vram.usable_size)
> - drm_info(&xe->drm, "VRAM[%u, %u]: CPU access limited to %pa\n", id,
> - tile->id, &tile->mem.vram.io_size);
"CPU access limited to" is helpful to quickly ID if you are on small bar
device, I would rather not drop this message or at least have a message
indicating this a small bar device without having to math.
Matt
> + drm_info(&xe->drm, "VRAM[%u, %u]: DPA range: [%pa-%llx], io range: [%pa-%llx]\n", id, tile->id,
> + &tile->mem.vram.base, tile->mem.vram.base + tile->mem.vram.actual_physical_size,
> + &tile->mem.vram.io_start, tile->mem.vram.io_start + tile->mem.vram.io_size);
>
> /* calculate total size using tile size to get the correct HW sizing */
> total_size += tile_size;
> --
> 2.26.3
>
next prev parent reply other threads:[~2023-08-11 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 2:44 [Intel-xe] [PATCH 1/3] drm/xe: Move the memory region struct out xe_tile Oak Zeng
2023-08-08 2:45 ` [Intel-xe] [PATCH 1/2] " Oak Zeng
2023-08-08 2:45 ` [Intel-xe] [PATCH 2/2] drm/xe: Improve vram info debug printing Oak Zeng
2023-08-11 18:25 ` Matthew Brost [this message]
2023-08-11 19:20 ` Zeng, Oak
2023-08-08 4:15 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Move the memory region struct out xe_tile Patchwork
2023-08-08 4:15 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-08 4:16 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-08 4:20 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-08 4:21 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-08 4:21 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-08 4:54 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-08-11 19:39 [Intel-xe] [PATCH 1/2] drm/xe: Make xe_mem_region struct Oak Zeng
2023-08-11 19:39 ` [Intel-xe] [PATCH 2/2] drm/xe: Improve vram info debug printing Oak Zeng
2023-08-11 20:40 ` Matthew Brost
2023-08-10 16:08 [Intel-xe] [PATCH 1/2] drm/xe: Make xe_mem_region struct Oak Zeng
2023-08-10 16:08 ` [Intel-xe] [PATCH 2/2] drm/xe: Improve vram info debug printing Oak Zeng
2023-08-08 2:43 [Intel-xe] [PATCH 1/3] drm/xe: Move the memory region struct out xe_tile Oak Zeng
2023-08-08 2:43 ` [Intel-xe] [PATCH 2/2] drm/xe: Improve vram info debug printing Oak Zeng
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=ZNZ9Dk16chiys59k@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=oak.zeng@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