From: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] lib/xe_query: fix vram_memory() and vram_if_possible()
Date: Thu, 6 Apr 2023 09:38:32 -0700 [thread overview]
Message-ID: <ZC71iFyroOKfxGTN@nvishwa1-DESK> (raw)
In-Reply-To: <20230406082157.258722-1-matthew.auld@intel.com>
On Thu, Apr 06, 2023 at 09:21:57AM +0100, Matthew Auld wrote:
>vram_memory() is meant to return VRAM if supported. If we call this on
>igpu it should return zero. There is at least one user relying on this
>in xe_mmap@vram, where we want to skip if the mask here is zero.
>
>vram_if_possible() should account for the per GT VRAM when returning
>the mask. Currently it just returns the mask for all VRAM instances.
>
>v2 (Niranjana):
> - Squash into a single patch
> - Fold in the differences from the version by Matt Brost & Zbigniew
>
LGTM.
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
>Reported-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
>Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
>Cc: Matthew Brost <matthew.brost@intel.com>
>---
> lib/xe/xe_query.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
>diff --git a/lib/xe/xe_query.c b/lib/xe/xe_query.c
>index 24a258a5e..2b627a78a 100644
>--- a/lib/xe/xe_query.c
>+++ b/lib/xe/xe_query.c
>@@ -380,7 +380,7 @@ uint64_t vram_memory(int fd, int gt)
> igt_assert(xe_dev);
> igt_assert(gt >= 0 && gt < xe_dev->number_gt);
>
>- return native_region_for_gt(xe_dev->gts, gt);
>+ return xe_has_vram(fd) ? native_region_for_gt(xe_dev->gts, gt) : 0;
> }
>
> /**
>@@ -393,11 +393,7 @@ uint64_t vram_memory(int fd, int gt)
> */
> uint64_t vram_if_possible(int fd, int gt)
> {
>- uint64_t regions = all_memory_regions(fd);
>- uint64_t system_memory = regions & 0x1;
>- uint64_t vram = regions & (~0x1);
>-
>- return vram ? vram : system_memory;
>+ return vram_memory(fd, gt) ?: system_memory(fd);
> }
>
> /**
>--
>2.39.2
>
next prev parent reply other threads:[~2023-04-06 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 8:21 [igt-dev] [PATCH i-g-t v2] lib/xe_query: fix vram_memory() and vram_if_possible() Matthew Auld
2023-04-06 10:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-06 16:38 ` Niranjana Vishwanathapura [this message]
2023-04-06 23:43 ` [igt-dev] ✓ Fi.CI.IGT: " 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=ZC71iFyroOKfxGTN@nvishwa1-DESK \
--to=niranjana.vishwanathapura@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.auld@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