All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases
Date: Wed, 5 Mar 2014 14:48:03 +0000	[thread overview]
Message-ID: <20140305144803.GC8496@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1393431465-31630-2-git-send-email-tvrtko.ursulin@linux.intel.com>

On Wed, Feb 26, 2014 at 04:17:43PM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> A set of userptr test cases to support the new feature.
> 
> For the eviction and swapping stress testing I have extracted
> some common behaviour from gem_evict_everything and made both
> test cases use it to avoid duplicating the code.
> 
> Both unsynchronized and synchronized userptr objects are
> tested but the latter set of tests will be skipped if kernel
> is compiled without MMU_NOTIFIERS.
> 
> Also, with 32-bit userspace swapping tests are skipped if
> the system has a lot more RAM than process address space.
> Forking swapping tests are not skipped since they can still
> trigger swapping by cumulative effect.
> 
> v2:
>    * Fixed dmabuf test.
>    * Added test for rejecting read-only.
>    * Fixed ioctl detection for latest kernel patch.
> 
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> +static void
> +copy(int fd, uint32_t dst, uint32_t src, unsigned int error)
> +{
> +	uint32_t batch[10];
> +	struct drm_i915_gem_relocation_entry reloc[2];
> +	struct drm_i915_gem_exec_object2 obj[3];
> +	struct drm_i915_gem_execbuffer2 exec;
> +	uint32_t handle;
> +	int ret;
> +
> +	batch[0] = XY_SRC_COPY_BLT_CMD |
> +		  XY_SRC_COPY_BLT_WRITE_ALPHA |
> +		  XY_SRC_COPY_BLT_WRITE_RGB | 6;

Hmm, you made blit() bdw-aware, but not this copy() routine?

As for the rest, I think we have good coverage.

What I would like to see exercised as well is mmap(fd), shm_open() and
sysv shmem.

Another thing to test is transfering our device fd over a unix socket to
another process and checking that we can continue to access the memory.
(That should just be the same as forking and continuing to use the
parent fd.)

I can think of more wacky vma to use, but I haven't thought of any
corner cases in the code that need exercising.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2014-03-05 14:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:17 [PATCH 0/3] tests: New userptr test case Tvrtko Ursulin
2014-02-26 16:17 ` [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin
2014-03-05 14:48   ` Chris Wilson [this message]
2014-03-12 13:21     ` Tvrtko Ursulin
2014-02-26 16:17 ` [PATCH 2/3] tests/gem_vmap_blits: Remove obsolete test case Tvrtko Ursulin
2014-02-26 16:17 ` [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-03-19 11:13 ` [PATCH 0/3] tests: New userptr test case Tvrtko Ursulin
2014-03-19 11:13   ` [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin
2014-04-18 17:10     ` Volkin, Bradley D
2014-04-23 13:33       ` Tvrtko Ursulin
2014-04-23 15:32         ` Volkin, Bradley D
2014-04-23 17:53           ` Daniel Vetter
2014-03-19 11:13   ` [PATCH 2/3] tests/gem_vmap_blits: Remove obsolete test case Tvrtko Ursulin
2014-04-17 23:20     ` Volkin, Bradley D
2014-03-19 11:13   ` [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-04-17 23:18     ` Volkin, Bradley D
2014-04-22 18:59       ` Daniel Vetter
2014-04-23 13:28       ` Tvrtko Ursulin
2014-04-23 15:24         ` Volkin, Bradley D
2014-04-23 16:38 ` [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin
2014-04-23 16:38   ` [PATCH 2/3] tests/gem_vmap_blits: Remove obsolete test case Tvrtko Ursulin
2014-04-23 17:12     ` Volkin, Bradley D
2014-04-23 16:38   ` [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-04-23 17:17     ` Volkin, Bradley D
2014-04-24  9:08       ` Tvrtko Ursulin
2014-04-23 17:24   ` [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Volkin, Bradley D
2014-04-24  9:07 ` [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-04-24 16:07   ` Volkin, Bradley D
2014-04-25 14:42 [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin

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=20140305144803.GC8496@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.