From: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 4/5] tests/xe/query: extend for CPU visible accounting
Date: Mon, 17 Apr 2023 08:54:16 +0300 [thread overview]
Message-ID: <dd5b612c-8e4f-1955-6c60-e66be55dde1b@intel.com> (raw)
In-Reply-To: <20230329115642.244296-5-matthew.auld@intel.com>
On 3/29/23 2:56 PM, Matthew Auld wrote:
> Print the visible size and how much is used. Also sanity check the
> values.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> ---
> tests/xe/xe_query.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tests/xe/xe_query.c b/tests/xe/xe_query.c
> index 3f038225..9367d65e 100644
> --- a/tests/xe/xe_query.c
> +++ b/tests/xe/xe_query.c
> @@ -228,6 +228,21 @@ test_query_mem_usage(int fd)
> igt_info("min_page_size=0x%x, max_page_size=0x%x\n",
> mem_usage->regions[i].min_page_size,
> mem_usage->regions[i].max_page_size);
> +
> + igt_info("visible size=%lluMiB\n",
> + mem_usage->regions[i].cpu_visible_size >> 20);
> + igt_info("visible used=%lluMiB\n",
> + mem_usage->regions[i].cpu_visible_used >> 20);
> +
> + igt_assert_lte_u64(mem_usage->regions[i].cpu_visible_size,
> + mem_usage->regions[i].total_size);
> + igt_assert_lte_u64(mem_usage->regions[i].cpu_visible_used,
> + mem_usage->regions[i].cpu_visible_size);
> + igt_assert_lte_u64(mem_usage->regions[i].cpu_visible_used,
> + mem_usage->regions[i].used);
> + igt_assert_lte_u64(mem_usage->regions[i].used -
> + mem_usage->regions[i].cpu_visible_used,
> + mem_usage->regions[i].total_size);
Although not exactly the cpu visible sanity check that the title of this
commit refers to, but there is no sanity check between used and total_size.
If it's not a semantic duplicate check, could you add this sanity check
as well?
Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> }
> dump_hex_debug(mem_usage, query.size);
> free(mem_usage);
next prev parent reply other threads:[~2023-04-17 5:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 11:56 [igt-dev] [PATCH i-g-t 0/5] IGT bits for small-bar Matthew Auld
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 1/5] xe: sync small-bar uapi Matthew Auld
2023-04-02 23:46 ` Gwan-gyeong Mun
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 2/5] lib/xe: add visible vram helpers Matthew Auld
2023-04-03 9:18 ` Gwan-gyeong Mun
2023-04-03 12:39 ` Matthew Auld
2023-04-03 14:17 ` Gwan-gyeong Mun
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 3/5] tests/xe: handle small-bar systems Matthew Auld
2023-04-05 12:53 ` Gwan-gyeong Mun
2023-05-17 17:03 ` Kamil Konieczny
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 4/5] tests/xe/query: extend for CPU visible accounting Matthew Auld
2023-04-17 5:54 ` Gwan-gyeong Mun [this message]
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 5/5] tests/xe/mmap: sanity check small-bar Matthew Auld
2023-03-29 12:39 ` [igt-dev] ✓ Fi.CI.BAT: success for IGT bits for small-bar Patchwork
2023-03-30 2:29 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-17 14:40 ` [igt-dev] ✗ Fi.CI.BUILD: failure for IGT bits for small-bar (rev2) 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=dd5b612c-8e4f-1955-6c60-e66be55dde1b@intel.com \
--to=gwan-gyeong.mun@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