From: Karolina Drobnik <karolina.drobnik@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v3 3/3] tests/api_intel_bb: Add misplaced_blitter test
Date: Wed, 2 Nov 2022 12:40:38 +0100 [thread overview]
Message-ID: <774290ae-4c80-a34f-cd84-f7354c628f2a@intel.com> (raw)
In-Reply-To: <Y2JVwQNFSZZl+Sgq@zkempczy-mobl2>
Hi Zbigniew,
Many thanks for reviewing my patches.
On 02.11.2022 12:34, Zbigniew Kempczyński wrote:
> On Wed, Nov 02, 2022 at 10:10:59AM +0100, Karolina Drobnik wrote:
>> Exercise intel_bb with a custom context engines layout.
>>
>> Signed-off-by: Karolina Drobnik <karolina.drobnik@intel.com>
>> ---
>> tests/i915/api_intel_bb.c | 65 +++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 63 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
>> index a881d6b0..c51804b1 100644
>> --- a/tests/i915/api_intel_bb.c
>> +++ b/tests/i915/api_intel_bb.c
>> @@ -40,11 +40,15 @@
>> #include "intel_bufops.h"
>> #include "i915/gem_vm.h"
>> #include "i915/i915_crc.h"
>> +#include "i915/i915_blt.h"
>>
>> #define PAGE_SIZE 4096
>>
>> -#define WIDTH 64
>> -#define HEIGHT 64
>> +#define WIDTH 64
>> +#define HEIGHT 64
>> +#define STRIDE (WIDTH * 4)
>> +#define SIZE (HEIGHT * STRIDE)
>> +
>> #define COLOR_00 0x00
>> #define COLOR_33 0x33
>> #define COLOR_77 0x77
>> @@ -1209,6 +1213,57 @@ static void full_batch(struct buf_ops *bops)
>> intel_bb_destroy(ibb);
>> }
>>
>> +static void misplaced_blitter(struct buf_ops *bops)
>> +{
>> + int i915 = buf_ops_get_fd(bops), i;
>> + struct intel_bb *ibb;
>> + struct intel_buf *src, *dst;
>> + uint64_t value, *psrc, *pdst;
>> +
>> + /* Use custom configuration with blitter at index 0 */
>> + const intel_ctx_cfg_t cfg = (intel_ctx_cfg_t) {
>> + .num_engines = 2,
>> + .engines = {
>> + { .engine_class = I915_ENGINE_CLASS_COPY,
>> + .engine_instance = 0
>> + },
>> + { .engine_class = I915_ENGINE_CLASS_RENDER,
>> + .engine_instance = 0
>> + },
>> + },
>> + };
>> +
>> + const intel_ctx_t *ctx = intel_ctx_create(i915, &cfg);
>> +
>> + ibb = intel_bb_create_with_context(i915, ctx->id, &ctx->cfg, PAGE_SIZE);
>> +
>> + /* Prepare for blitter copy, done to verify we found the blitter engine */
>> + src = intel_buf_create(bops, WIDTH, HEIGHT, 32, 0, I915_TILING_NONE,
>> + I915_COMPRESSION_NONE);
>> + dst = intel_buf_create(bops, WIDTH, HEIGHT, 32, 0, I915_TILING_NONE,
>> + I915_COMPRESSION_NONE);
>> + psrc = intel_buf_device_map(src, true);
>> + pdst = intel_buf_device_map(dst, true);
>> +
>> + /* Populate src with dummy values */
>> + memset(&value, COLOR_33, 8);
>> + for (i = 0; i < SIZE / sizeof(value); i++)
>> + memset(&psrc[i], value, 8);
>> +
>> + intel_bb_copy_intel_buf(ibb, src, dst, SIZE);
>> + intel_bb_flush_blit(ibb);
>> + intel_bb_sync(ibb);
>> +
>> + /* Expect to see a successful copy */
>> + igt_assert_eq(memcmp(pdst, psrc, SIZE), 0);
>
> You may get memcpy() result here...
>
>> +
>> + intel_buf_unmap(src);
>> + intel_buf_unmap(dst);
>> +
>> + intel_bb_destroy(ibb);
>> + intel_ctx_destroy(i915, ctx);
>
> and assert here. Assuming you'll destroy src/dst as they are unmapped only.
> There's problem of our tests - if they assert we have not freed allocations.
> For your case there's single assertion so you can just catch this return
> and assert on the end.
Right, I wasn't sure if we free them after the assert. I'll correct it
in the next version.
All the best,
Karolina
> --
> Zbigniew
>
>> +}
>> +
>> static int render(struct buf_ops *bops, uint32_t tiling, bool do_reloc,
>> uint32_t width, uint32_t height)
>> {
>> @@ -1581,6 +1636,12 @@ igt_main_args("dpibc:", NULL, help_str, opt_handler, NULL)
>> igt_subtest("full-batch")
>> full_batch(bops);
>>
>> + igt_describe("Execute intel_bb with set of engines provided by userspace");
>> + igt_subtest("misplaced-blitter") {
>> + gem_require_contexts(i915);
>> + misplaced_blitter(bops);
>> + }
>> +
>> igt_subtest_with_dynamic("render") {
>> for (i = 0; i < ARRAY_SIZE(tests); i++) {
>> const struct test *t = &tests[i];
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2022-11-02 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 9:10 [igt-dev] [PATCH i-g-t v3 0/3] Add support for intel_ctx_t in intel_bb Karolina Drobnik
2022-11-02 9:10 ` [igt-dev] [PATCH i-g-t v3 1/3] lib/intel_batchbuffer: Extend __intel_bb_create to handle context config Karolina Drobnik
2022-11-02 11:26 ` Zbigniew Kempczyński
2022-11-02 9:10 ` [igt-dev] [PATCH i-g-t v3 2/3] lib/intel_batchbuffer: Add support for custom engine layouts Karolina Drobnik
2022-11-02 9:10 ` [igt-dev] [PATCH i-g-t v3 3/3] tests/api_intel_bb: Add misplaced_blitter test Karolina Drobnik
2022-11-02 11:34 ` Zbigniew Kempczyński
2022-11-02 11:40 ` Karolina Drobnik [this message]
2022-11-02 12:13 ` [igt-dev] ✓ Fi.CI.BAT: success for Add support for intel_ctx_t in intel_bb (rev3) Patchwork
2022-11-02 17:17 ` [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=774290ae-4c80-a34f-cd84-f7354c628f2a@intel.com \
--to=karolina.drobnik@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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