public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_mmap_gtt: Test mmap_offset lifetime
Date: Tue, 13 Aug 2019 13:44:11 +0300	[thread overview]
Message-ID: <673f6878-1ac1-1d09-d9f8-ce8ce4ee7812@linux.intel.com> (raw)
In-Reply-To: <20190810123821.24009-1-chris@chris-wilson.co.uk>



On 10/08/2019 15.38, Chris Wilson wrote:
> Closing the object on another file should not affect the local
> mmap_offset.
> 

Thanks for this! It helped squeezed the bug out of mmap_offset.

Reviewed-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>


> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
> ---
>  tests/i915/gem_mmap_gtt.c | 40 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
> 
> diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
> index 6f3a9c36e..8eff91850 100644
> --- a/tests/i915/gem_mmap_gtt.c
> +++ b/tests/i915/gem_mmap_gtt.c
> @@ -322,6 +322,44 @@ test_pf_nonblock(int i915)
>  	igt_spin_free(i915, spin);
>  }
>  
> +static void
> +test_isolation(int i915)
> +{
> +	struct drm_i915_gem_mmap_gtt mmap_arg;
> +	int A = gem_reopen_driver(i915);
> +	int B = gem_reopen_driver(i915);
> +	uint64_t offset_a, offset_b;
> +	uint32_t a, b;
> +	void *ptr;
> +
> +	a = gem_create(A, 4096);
> +	b = gem_open(B, gem_flink(A, a));
> +
> +	mmap_arg.handle = a;
> +	do_ioctl(A, DRM_IOCTL_I915_GEM_MMAP_GTT, &mmap_arg);
> +	offset_a = mmap_arg.offset;
> +
> +	mmap_arg.handle = b;
> +	do_ioctl(B, DRM_IOCTL_I915_GEM_MMAP_GTT, &mmap_arg);
> +	offset_b = mmap_arg.offset;
> +
> +	igt_info("A: {fd:%d, handle:%d, offset:%"PRIx64"}\n",
> +		 A, a, offset_a);
> +	igt_info("B: {fd:%d, handle:%d, offset:%"PRIx64"}\n",
> +		 B, b, offset_b);
> +
> +	close(B);
> +
> +	ptr = mmap64(0, 4096, PROT_READ, MAP_SHARED, A, offset_a);
> +	igt_assert(ptr != MAP_FAILED);
> +	munmap(ptr, 4096);
> +
> +	close(A);
> +
> +	ptr = mmap64(0, 4096, PROT_READ, MAP_SHARED, A, offset_a);
> +	igt_assert(ptr == MAP_FAILED);
> +}
> +
>  static void
>  test_write_gtt(int fd)
>  {
> @@ -945,6 +983,8 @@ igt_main
>  		test_write_cpu_read_gtt(fd);
>  	igt_subtest("basic-wc")
>  		test_wc(fd);
> +	igt_subtest("isolation")
> +		test_isolation(fd);
>  	igt_subtest("pf-nonblock")
>  		test_pf_nonblock(fd);
>  
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      parent reply	other threads:[~2019-08-13 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 12:38 [igt-dev] [PATCH i-g-t] i915/gem_mmap_gtt: Test mmap_offset lifetime Chris Wilson
2019-08-10 13:41 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-08-11  5:18 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-08-13 10:44 ` Abdiel Janulgue [this message]

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=673f6878-1ac1-1d09-d9f8-ce8ce4ee7812@linux.intel.com \
    --to=abdiel.janulgue@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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