public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests/gem_softpin: New tests for softpin feature
Date: Wed, 2 Dec 2015 10:45:42 +0000	[thread overview]
Message-ID: <565ECBD6.3060903@linux.intel.com> (raw)
In-Reply-To: <565EC6F2.6030000@linux.intel.com>


Hi,

On 02/12/15 10:24, Tvrtko Ursulin wrote:
> On 01/12/15 11:20, Vinay Belgaumkar wrote:
>> These tests exercise the userptr ioctl to create shared buffers
>> between CPU and GPU. They contain error and normal usage scenarios.
>> They also contain a couple of stress tests which copy buffers between
>> CPU and GPU. These tests rely on the softpin patch in order to pin
>> buffers
>> to a certain VA.
>>
>> Caveat: These tests were designed to run on 64-bit system. Future work
>> includes adding logic to ensure these tests can run on 32-bit systems
>> with
>> PPGTT support. Some tests are currently disabled for 32-bit systems
>> for that
>> reason.
>>
>> v2: Added cc and signed-off-by fields
>>
>> v3: Fixed review comments, added helper functions. Removed userptr error
>> scenarios covered by existing userptr tests. Modified stress test to have
>> 100K buffers, it now runs for ~30 mins, checks every element has been
>> written
>> to correctly, and pins buffers at different VMAs.
>>
>> v4: Changed name to gem_softpin
>>
>> v5: More fixes. Removed the file based tests, will move them to
>> userptr tests.
>> Added a function that validates appropriate PPGTT support before
>> running tests.
>> Optimized stack space and memory footprint in stress test. Removed the
>> eviction
>> test, will add it back after verifying proper functionality.
>>
>> v6: Split basic test into userptr and bo
>> Fixed some coding style issues.
>>
>> v7: Enhanced invalid vma pinning test to verify 32-bit PPGTT
>> functionality.
>> Enabled the test for 32-bit PPGTT systems, and verify pinning fails above
>> 32-bit addresses. Enhanced the high adress pinning test to ensure pinning
>> fails when EXEC_OBJECT_PINNED flag is not used. Some more cosmetic
>> fixes to
>> close buffer handles. Changed userptr function to used synchronized
>> operations.
>>
>> v8: Minor change to high address pinning test as per comment.
>>
>> Cc: Michel Thierry <michel.thierry@intel.com>
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>>   tests/.gitignore       |    1 +
>>   tests/Makefile.sources |    1 +
>>   tests/gem_softpin.c    | 1049
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>>   3 files changed, 1051 insertions(+)
>>   create mode 100644 tests/gem_softpin.c
>
> I could find some more style issues but it looks functionally reasonable
> for the basic coverage. So:
>
>    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Now comes the hard part - following up on the promise to extend with
> more test cases here and elsewhere. :)

I take it back! :)

One thing is, you are not using I915_PARAM_HAS_EXEC_SOFTPIN to 
gracefully skip tests when kernel does not have the softpin feature.

Regards,

Tvrtko

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-02 10:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 11:20 [PATCH i-g-t] tests/gem_softpin: New tests for softpin feature Vinay Belgaumkar
2015-12-02 10:24 ` Tvrtko Ursulin
2015-12-02 10:45   ` Tvrtko Ursulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-03  8:36 Vinay Belgaumkar
2015-12-03 16:42 ` Tvrtko Ursulin
2015-12-08 11:57 ` Michel Thierry
2015-12-08 12:16   ` Tvrtko Ursulin
2015-12-09 10:32     ` Tvrtko Ursulin
2015-12-02 12:24 Vinay Belgaumkar
2015-12-03 11:42 ` Tvrtko Ursulin
2015-11-30 18:22 Vinay Belgaumkar
2015-12-01 10:35 ` Tvrtko Ursulin
2015-12-04  9:45   ` Daniel Vetter
2015-11-29 12:43 Vinay Belgaumkar
2015-11-30 14:16 ` Tvrtko Ursulin
2015-11-25 14:44 Vinay Belgaumkar
2015-11-26 16:09 ` Tvrtko Ursulin
2015-11-19 22:29 Vinay Belgaumkar
2015-11-20 16:20 ` 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=565ECBD6.3060903@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vinay.belgaumkar@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