From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [PATCH v4] drm/i915: Fallback to using unmappable memory for scanout
Date: 25 Mar 2015 10:30:23 -0700 [thread overview]
Message-ID: <2d8c1b$kdp44e@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1427287487-10950-1-git-send-email-chris@chris-wilson.co.uk>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6049
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -6 269/269 263/269
ILK 303/303 303/303
SNB 304/304 304/304
IVB 338/338 338/338
BYT 287/287 287/287
HSW 362/362 362/362
BDW 310/310 310/310
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
PNV igt@gem_userptr_blits@coherency-sync CRASH(3)PASS(3) CRASH(2)
*PNV igt@gem_fence_thrash@bo-write-verify-none PASS(2) FAIL(1)PASS(1)
PNV igt@gem_userptr_blits@minor-unsync-interruptible DMESG_WARN(1)PASS(3) DMESG_WARN(1)PASS(1)
WARNING:at_drivers/gpu/drm/i915/i915_gem_evict.c:#i915_gem_evict_vm[i915]()@WARNING:.* at .* i915_gem_evict_vm+0x
PNV igt@gem_userptr_blits@minor-unsync-normal DMESG_WARN(1)PASS(2) DMESG_WARN(1)PASS(1)
WARNING:at_drivers/gpu/drm/i915/i915_gem_evict.c:#i915_gem_evict_vm[i915]()@WARNING:.* at .* i915_gem_evict_vm+0x
*PNV igt@gem_fence_thrash@bo-write-verify-threaded-none PASS(2) CRASH(1)PASS(1)
*PNV igt@gem_unfence_active_buffers PASS(2) NO_RESULT(1)PASS(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-03-25 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 22:08 [PATCH] drm/i915: Fallback to using unmappable memory for scanout Chris Wilson
2015-03-19 10:53 ` Deepak S
2015-03-19 11:27 ` Chris Wilson
2015-03-19 11:29 ` [PATCH v2] " Chris Wilson
2015-03-19 13:01 ` Deepak S
2015-03-19 13:10 ` Chris Wilson
2015-03-19 13:13 ` Deepak S
2015-03-19 16:34 ` Daniel Vetter
2015-03-19 16:51 ` Chris Wilson
2015-03-19 16:35 ` Daniel Vetter
2015-03-19 16:50 ` Chris Wilson
2015-03-20 10:29 ` Daniel Vetter
2015-03-20 10:49 ` Chris Wilson
2015-03-20 14:36 ` Daniel Vetter
2015-03-20 14:52 ` Ville Syrjälä
2015-03-19 16:39 ` Damien Lespiau
2015-03-19 16:54 ` Chris Wilson
2015-03-19 21:57 ` shuang.he
2015-03-25 12:21 ` Jani Nikula
2015-03-25 12:40 ` [PATCH v3] " Chris Wilson
2015-03-25 15:07 ` shuang.he
2015-03-25 12:44 ` [PATCH v4] " Chris Wilson
2015-03-25 13:17 ` Daniel Vetter
2015-03-25 17:30 ` shuang.he [this message]
2015-03-19 15:34 ` [PATCH] " shuang.he
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$kdp44e@fmsmga001.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=ethan.gao@intel.com \
--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 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.