From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Volkin, Bradley D" <bradley.d.volkin@intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact
Date: Thu, 24 Apr 2014 10:08:56 +0100 [thread overview]
Message-ID: <5358D4A8.1060107@linux.intel.com> (raw)
In-Reply-To: <20140423171749.GD23344@bdvolkin-ubuntu-desktop>
On 04/23/2014 06:17 PM, Volkin, Bradley D wrote:
[snip]
>> +static int gem_userptr(int fd, void *ptr, int size, int read_only, uint32_t *handle)
>> +{
>> + struct local_i915_gem_userptr userptr;
>> + int ret;
>> +
>> + userptr.user_ptr = (uintptr_t)ptr;
>> + userptr.user_size = size;
>> + userptr.flags = userptr_flags;
>> + if (read_only)
>> + userptr.flags |= LOCAL_I915_USERPTR_READ_ONLY;
>> +
>> + ret = drmIoctl(fd, LOCAL_IOCTL_I915_GEM_USERPTR, &userptr);
>> + if (ret)
>> + ret = errno;
>> + igt_skip_on_f(ret == ENODEV &&
>> + (userptr_flags & LOCAL_I915_USERPTR_UNSYNCHRONIZED) == 0,
>> + "Skipping, synchronized mappings with no kernel CONFIG_MMU_NOTIFIER?");
>
> I missed it the first time around, but the condition here doesn't
> match the other test; it's missing the '&& !read_only'. It looks
> like read_only will always be 0 in this test though, so probably
> not an issue.
>
> Reviewed-by: Brad Volkin <bradley.d.volkin@intel.com>
Good catch! It does not matter in the benchmark but I've sent a respin
for consistency and clarity.
Thanks,
Tvrtko
next prev parent reply other threads:[~2014-04-24 9:09 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-04-25 14:42 [PATCH 1/3] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin
2014-04-25 14:42 ` [PATCH 3/3] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact 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=5358D4A8.1060107@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=bradley.d.volkin@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.