From: "Laguna, Lukasz" <lukasz.laguna@intel.com>
To: Marcin Bernatowicz <marcin.bernatowicz@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: jakub1.kolakowski@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] xe_create: create-big-vram subtest
Date: Tue, 21 Nov 2023 14:56:03 +0100 [thread overview]
Message-ID: <3adf02ee-174a-59d6-f958-a4defe6134bc@intel.com> (raw)
In-Reply-To: <20231121135020.15451-1-marcin.bernatowicz@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3828 bytes --]
On 11/21/2023 14:50, Marcin Bernatowicz wrote:
> Validates the creation of significant Buffer Objects (BO) within VRAM,
> accounting for 75% of the CPU-visible VRAM size.
maybe create BO with CPU-*available *VRAM size (CPU-visible VRAM size -
used VRAM)?
> The size of the created BO can be adjusted using command line parameters,
> with '-S' representing BO size in MB,
> and '-p' representing BO size as a percentage of the VRAM size.
>
> v2: rebased, updated to uAPI changes (DRM_XE_VM_CREATE_FLAG_ASYNC_DEFAULT),
> after review corrections: 1024UL -> 1024ULL,
> int -> unsigned int (Kamil)
>
> Signed-off-by: Marcin Bernatowicz<marcin.bernatowicz@intel.com>
> ---
> tests/intel/xe_create.c | 80 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 79 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_create.c b/tests/intel/xe_create.c
> index f4633cfb3..3ff9bb750 100644
> --- a/tests/intel/xe_create.c
> +++ b/tests/intel/xe_create.c
> @@ -18,6 +18,14 @@
>
> #define PAGE_SIZE 0x1000
>
> +static struct param {
> + unsigned int size_MB;
nit: size_mb?
> + unsigned int vram_percent;
> +} params = {
> + .size_MB = 0,
> + .vram_percent = 75,
> +};
> +
> static int __create_bo(int fd, uint32_t vm, uint64_t size, uint32_t flags,
> uint32_t *handlep)
> {
> @@ -214,7 +222,73 @@ static void create_massive_size(int fd)
> }
> }
>
> -igt_main
> +/**
> + * SUBTEST: create-big-vram
> + * Functionality: BO creation
> + * Test category: functionality test
> + * Description: Validates the creation of substantial BO within VRAM
> + * (constituting 75% of the CPU-visible VRAM).
> + */
> +static void create_big_vram(int fd)
> +{
> + uint64_t bo_size, size, vram_size, alignment;
> + uint32_t bo_handle;
> + char *bo_ptr = NULL;
> + uint64_t vm = 0;
> + int gt;
> +
> + igt_require(xe_has_vram(fd));
> + alignment = xe_get_default_alignment(fd);
> + vm = xe_vm_create(fd, DRM_XE_VM_CREATE_FLAG_ASYNC_DEFAULT, 0);
> +
> + xe_for_each_gt(fd, gt) {
> + vram_size = xe_visible_vram_size(fd, gt);
> + bo_size = params.size_MB ? params.size_MB * 1024ULL * 1024ULL
> + : ALIGN(vram_size * params.vram_percent / 100, alignment);
if you decide to don't use percentages you can use (xe_visible_vram_size
- mem_region.used) when params.size_MB is 0 here. In such case I'm not
sure if -p option is needed.
> + igt_debug("gt%u bo_size=%lu visible_vram_size=%lu\n", gt, bo_size, vram_size);
> +
> + igt_assert_eq(0, __create_bo(fd, vm, bo_size, vram_memory(fd, gt), &bo_handle));
nit: xe_bo_create_flags can be used instead
> + bo_ptr = xe_bo_map(fd, bo_handle, bo_size);
> + size = bo_size - 1;
> + while (size > SZ_64K) {
> + igt_assert_eq(0, READ_ONCE(bo_ptr[size]));
> + WRITE_ONCE(bo_ptr[size], 'A');
> + igt_assert_eq('A', READ_ONCE(bo_ptr[size]));
> + size >>= 1;
> + }
> +
> + igt_assert_eq(0, bo_ptr[0]);
> + munmap(bo_ptr, bo_size);
> + gem_close(fd, bo_handle);
> + }
> +
> + xe_vm_destroy(fd, vm);
> +}
> +
> +static int opt_handler(int opt, int opt_index, void *data)
> +{
> + switch (opt) {
> + case 'S':
> + params.size_MB = atoi(optarg);
> + igt_debug("Size MB: %d\n", params.size_MB);
> + break;
> + case 'p':
> + params.vram_percent = atoi(optarg);
> + igt_debug("Percent of VRAM: %d\n", params.vram_percent);
> + break;
> + default:
> + return IGT_OPT_HANDLER_ERROR;
> + }
> +
> + return IGT_OPT_HANDLER_SUCCESS;
> +}
> +
> +const char *help_str =
> + " -S\tBO size in MB\n"
> + " -p\tPercent of VRAM for BO (default 75% of visible VRAM size)\n"
> + ;
> +
> +igt_main_args("S:p:", NULL, help_str, opt_handler, NULL)
> {
> int xe;
>
> @@ -254,6 +328,10 @@ igt_main
> }
>
>
> + igt_subtest("create-big-vram") {
> + create_big_vram(xe);
> + }
> +
> igt_fixture
> drm_close_driver(xe);
> }
[-- Attachment #2: Type: text/html, Size: 4766 bytes --]
next prev parent reply other threads:[~2023-11-21 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 13:50 [igt-dev] [PATCH i-g-t] xe_create: create-big-vram subtest Marcin Bernatowicz
2023-11-21 13:56 ` Laguna, Lukasz [this message]
2023-11-21 15:08 ` [igt-dev] ✓ Fi.CI.BAT: success for xe_create: create-big-vram subtest (rev2) Patchwork
2023-11-21 15:42 ` [igt-dev] [PATCH i-g-t] xe_create: create-big-vram subtest Matthew Auld
2023-11-22 10:26 ` Bernatowicz, Marcin
2023-11-21 16:31 ` [igt-dev] ✓ CI.xeBAT: success for xe_create: create-big-vram subtest (rev2) Patchwork
2023-11-22 9:28 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-11-22 10:19 [igt-dev] [PATCH i-g-t] xe_create: create-big-vram subtest Marcin Bernatowicz
2023-11-22 11:04 ` Laguna, Lukasz
2023-11-22 16:16 ` Kamil Konieczny
2023-11-23 10:24 ` Bernatowicz, Marcin
2023-11-13 19:20 Marcin Bernatowicz
2023-11-20 17:51 ` Kamil Konieczny
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=3adf02ee-174a-59d6-f958-a4defe6134bc@intel.com \
--to=lukasz.laguna@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=marcin.bernatowicz@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