From: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
To: Pravalika Gurram <pravalika.gurram@intel.com>
Cc: igt-dev@lists.freedesktop.org, sai.gowtham.ch@intel.com,
katarzyna.piecielska@intel.com
Subject: Re: [PATCH i-g-t 2/2] tests/intel/xe_exec_compute_mode: LR mode should use command or render
Date: Wed, 16 Oct 2024 08:24:54 +0200 [thread overview]
Message-ID: <20241016062454.sour3dim4awzbf5f@zkempczy-mobl2> (raw)
In-Reply-To: <20241015141826.4186247-3-pravalika.gurram@intel.com>
On Tue, Oct 15, 2024 at 07:48:26PM +0530, Pravalika Gurram wrote:
> Spinner which has to run in LR mode should be
> executed on compute or render command streamer.
> Stop assuming engine id is equal to 1
> and use 'xe_find_engine_by_class'
> helper to find engine by its class.
> use 'xe_find_engine_by_class' with required engine class
> to get the engine info.
>
> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Signed-off-by: Pravalika Gurram <pravalika.gurram@intel.com>
> ---
> tests/intel/xe_exec_compute_mode.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel/xe_exec_compute_mode.c b/tests/intel/xe_exec_compute_mode.c
> index 82e607848..f62859689 100644
> --- a/tests/intel/xe_exec_compute_mode.c
> +++ b/tests/intel/xe_exec_compute_mode.c
> @@ -457,11 +457,18 @@ static void lr_mode_workload(int fd)
> uint64_t ahnd;
> uint32_t bo;
> uint32_t ts_1, ts_2;
> + uint32_t num_engines;
>
> vm = xe_vm_create(fd, DRM_XE_VM_CREATE_FLAG_LR_MODE, 0);
> ahnd = intel_allocator_open(fd, 0, INTEL_ALLOCATOR_RELOC);
> bo_size = xe_bb_size(fd, sizeof(*spin));
> - engine = xe_engine(fd, 1);
I've checked this on ADL and for me bcs is fine so I don't think
we should merge this change in this form.
However as engines may be on different indices on different platforms
I would at least pick engine via:
engine = xe_find_engine_by_class(fd, DRM_XE_ENGINE_CLASS_COPY);
We'll avoid issue whereindex for bcs will be different than 1 in this case.
--
Zbigniew
> +
> + num_engines = xe_number_engines(fd);
> + engine = xe_find_engine_by_class(fd, DRM_XE_ENGINE_CLASS_COMPUTE);
> + if (engine == NULL)
> + engine = xe_find_engine_by_class(fd, DRM_XE_ENGINE_CLASS_RENDER);
> + igt_skip_on_f((engine == NULL), "num_engines %d\n", num_engines);
> +
> bo = xe_bo_create(fd, vm, bo_size, vram_if_possible(fd, engine->instance.gt_id), 0);
> spin = xe_bo_map(fd, bo, bo_size);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-10-16 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:18 [PATCH i-g-t 0/2] xe_find_engine_by_class helper Pravalika Gurram
2024-10-15 14:18 ` [PATCH i-g-t 1/2] lib/xe/xe_query: " Pravalika Gurram
2024-10-15 15:49 ` Zbigniew Kempczyński
2024-10-15 14:18 ` [PATCH i-g-t 2/2] tests/intel/xe_exec_compute_mode: LR mode should use command or render Pravalika Gurram
2024-10-15 15:54 ` Zbigniew Kempczyński
2024-10-16 6:24 ` Zbigniew Kempczyński [this message]
2024-10-15 18:52 ` ✓ CI.xeBAT: success for xe_find_engine_by_class helper Patchwork
2024-10-15 18:59 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-15 19:52 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-16 4:14 ` ✗ CI.xeFULL: " 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=20241016062454.sour3dim4awzbf5f@zkempczy-mobl2 \
--to=zbigniew.kempczynski@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=katarzyna.piecielska@intel.com \
--cc=pravalika.gurram@intel.com \
--cc=sai.gowtham.ch@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