From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH 3/3] drm/i915: Use a task to cancel the userptr on invalidate_range
Date: 02 Jul 2015 09:40:34 -0700 [thread overview]
Message-ID: <2d8c1b$m14nbm@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1435683333-17844-3-git-send-email-chris@chris-wilson.co.uk>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6689
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
ILK 302/302 302/302
SNB 312/316 312/316
IVB 343/343 343/343
BYT -1 287/287 286/287
HSW 380/380 380/380
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*BYT igt@gem_userptr_blits@sync-unmap-cycles PASS(1) FAIL(1)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-02 16:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 10:59 [PATCH] tests/gem_userptr_blits: subtests for MAP_FIXED mappings of regular bo Michał Winiarski
2015-06-29 11:09 ` [PATCH] drm/i915: Fix userptr deadlock with MAP_FIXED Chris Wilson
2015-06-29 11:17 ` [PATCH v2] " Chris Wilson
2015-06-29 15:57 ` Michał Winiarski
2015-06-29 15:57 ` Michał Winiarski
2015-06-30 14:52 ` Tvrtko Ursulin
2015-06-30 14:52 ` [Intel-gfx] " Tvrtko Ursulin
2015-06-30 15:31 ` Chris Wilson
2015-06-30 15:47 ` Chris Wilson
2015-06-29 14:01 ` [PATCH] tests/gem_userptr_blits: subtests for MAP_FIXED mappings of regular bo Tvrtko Ursulin
2015-06-29 14:07 ` Chris Wilson
2015-06-29 14:15 ` Tvrtko Ursulin
2015-06-29 14:25 ` Chris Wilson
2015-06-29 14:56 ` Tvrtko Ursulin
2015-06-29 15:03 ` Chris Wilson
2015-06-30 15:01 ` [PATCH v2] tests/gem_userptr_blits: subtests for MAP_FIXED mappings of regular BO Michał Winiarski
2015-06-30 16:55 ` [PATCH 1/3] drm/i915: Only update the current userptr worker Chris Wilson
2015-06-30 16:55 ` [PATCH 2/3] drm/i915: Fix userptr deadlock with MAP_FIXED Chris Wilson
2015-07-01 11:14 ` Tvrtko Ursulin
2015-07-01 11:14 ` [Intel-gfx] " Tvrtko Ursulin
2015-07-01 11:29 ` Chris Wilson
2015-06-30 16:55 ` [PATCH 3/3] drm/i915: Use a task to cancel the userptr on invalidate_range Chris Wilson
2015-07-01 12:56 ` Tvrtko Ursulin
2015-07-03 11:00 ` Chris Wilson
2015-07-02 16:40 ` shuang.he [this message]
2015-07-03 11:03 ` [PATCH] " Chris Wilson
2015-07-01 9:48 ` [PATCH 1/3] drm/i915: Only update the current userptr worker Tvrtko Ursulin
2015-07-01 9:59 ` Chris Wilson
2015-07-01 10:58 ` Tvrtko Ursulin
2015-07-01 11:09 ` Chris Wilson
2015-07-01 12:26 ` Tvrtko Ursulin
2015-07-01 13:11 ` Chris Wilson
2015-07-03 10:48 ` Michał Winiarski
2015-07-03 10:53 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 11:34 Chris Wilson
2015-10-01 11:34 ` [PATCH 3/3] drm/i915: Use a task to cancel the userptr on invalidate_range Chris Wilson
2015-10-06 12:04 ` Daniel Vetter
2015-10-06 12:25 ` Chris Wilson
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='2d8c1b$m14nbm@fmsmga001.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lei.a.liu@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.