Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/i915/gem_exec_balancer: exercise dmabuf import
Date: Thu, 24 Nov 2022 13:59:18 +0100	[thread overview]
Message-ID: <b2df860d-9963-a00f-45eb-57770ec7864d@intel.com> (raw)
In-Reply-To: <20221118155335.635430-1-matthew.auld@intel.com>



On 18.11.2022 16:53, Matthew Auld wrote:
> With parallel submission it should be easy to get a fence array as the
> output fence. Try importing this into dma-buf reservation object, to see
> if anything explodes.
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/7532
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> ---
>   tests/i915/gem_exec_balancer.c | 39 ++++++++++++++++++++++++++++++++++
>   1 file changed, 39 insertions(+)
>
> diff --git a/tests/i915/gem_exec_balancer.c b/tests/i915/gem_exec_balancer.c
> index 4300dbd1..fdae8de5 100644
> --- a/tests/i915/gem_exec_balancer.c
> +++ b/tests/i915/gem_exec_balancer.c
> @@ -37,6 +37,7 @@
>   #include "igt_sysfs.h"
>   #include "igt_types.h"
>   #include "sw_sync.h"
> +#include <linux/dma-buf.h>
>   
>   IGT_TEST_DESCRIPTION("Exercise in-kernel load-balancing");
>   
> @@ -2856,6 +2857,24 @@ static void logical_sort_siblings(int i915,
>   #define PARALLEL_SUBMIT_FENCE		(0x1 << 3)
>   #define PARALLEL_CONTEXTS		(0x1 << 4)
>   #define PARALLEL_VIRTUAL		(0x1 << 5)
> +#define PARALLEL_OUT_FENCE_DMABUF	(0x1 << 6)
> +
> +struct igt_dma_buf_sync_file {
> +        __u32 flags;
> +        __s32 fd;
> +};
> +
> +#define IGT_DMA_BUF_IOCTL_EXPORT_SYNC_FILE _IOWR(DMA_BUF_BASE, 2, struct igt_dma_buf_sync_file)
> +#define IGT_DMA_BUF_IOCTL_IMPORT_SYNC_FILE _IOW(DMA_BUF_BASE, 3, struct igt_dma_buf_sync_file)
> +
> +static void dmabuf_import_sync_file(int dmabuf, uint32_t flags, int sync_fd)
> +{
> +        struct igt_dma_buf_sync_file arg;
> +
> +        arg.flags = flags;
> +        arg.fd = sync_fd;
> +        do_ioctl(dmabuf, IGT_DMA_BUF_IOCTL_IMPORT_SYNC_FILE, &arg);
> +}

Wouldn't be good to move code above to some common lib?
Anyway:
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Regards
Andrzej

>   
>   static void parallel_thread(int i915, unsigned int flags,
>   			    struct i915_engine_class_instance *siblings,
> @@ -2871,6 +2890,8 @@ static void parallel_thread(int i915, unsigned int flags,
>   	uint32_t target_bo_idx = 0;
>   	uint32_t first_bb_idx = 1;
>   	intel_ctx_cfg_t cfg;
> +	uint32_t dmabuf_handle;
> +	int dmabuf;
>   
>   	igt_assert(bb_per_execbuf < 32);
>   
> @@ -2924,11 +2945,20 @@ static void parallel_thread(int i915, unsigned int flags,
>   	execbuf.buffers_ptr = to_user_pointer(obj);
>   	execbuf.rsvd1 = ctx->id;
>   
> +	if (flags & PARALLEL_OUT_FENCE_DMABUF) {
> +		dmabuf_handle = gem_create(i915, 4096);
> +		dmabuf = prime_handle_to_fd(i915, dmabuf_handle);
> +	}
> +
>   	for (n = 0; n < PARALLEL_BB_LOOP_COUNT; ++n) {
>   		execbuf.flags &= ~0x3full;
>   		gem_execbuf_wr(i915, &execbuf);
>   
>   		if (flags & PARALLEL_OUT_FENCE) {
> +			if (flags & PARALLEL_OUT_FENCE_DMABUF)
> +				dmabuf_import_sync_file(dmabuf, DMA_BUF_SYNC_WRITE,
> +							execbuf.rsvd2 >> 32);
> +
>   			igt_assert_eq(sync_fence_wait(execbuf.rsvd2 >> 32,
>   						      1000), 0);
>   			igt_assert_eq(sync_fence_status(execbuf.rsvd2 >> 32), 1);
> @@ -2959,6 +2989,11 @@ static void parallel_thread(int i915, unsigned int flags,
>   	if (fence)
>   		close(fence);
>   
> +	if (flags & PARALLEL_OUT_FENCE_DMABUF) {
> +		gem_close(i915, dmabuf_handle);
> +		close(dmabuf);
> +	}
> +
>   	check_bo(i915, obj[target_bo_idx].handle,
>   		 bb_per_execbuf * PARALLEL_BB_LOOP_COUNT, true);
>   
> @@ -3420,6 +3455,10 @@ igt_main
>   		igt_subtest("parallel-out-fence")
>   			parallel(i915, PARALLEL_OUT_FENCE);
>   
> +		igt_subtest("parallel-out-fence-import-dmabuf")
> +			parallel(i915, PARALLEL_OUT_FENCE |
> +				 PARALLEL_OUT_FENCE_DMABUF);
> +
>   		igt_subtest("parallel-keep-in-fence")
>   			parallel(i915, PARALLEL_OUT_FENCE | PARALLEL_IN_FENCE);
>   


  reply	other threads:[~2022-11-24 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 15:53 [Intel-gfx] [PATCH i-g-t] tests/i915/gem_exec_balancer: exercise dmabuf import Matthew Auld
2022-11-24 12:59 ` Andrzej Hajda [this message]
2022-11-25  9:24 ` Kamil Konieczny
2022-11-25 10:26 ` 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=b2df860d-9963-a00f-45eb-57770ec7864d@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@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