From: shuang.he@intel.com
To: shuang.he@intel.com, intel-gfx@lists.freedesktop.org,
thomas.daniel@intel.com
Subject: Re: [PATCH] drm/i915: Don't pin LRC in GGTT when dumping in debugfs
Date: 02 Dec 2014 17:39:21 -0800 [thread overview]
Message-ID: <84c8a8$id1bro@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1417526478-27010-1-git-send-email-thomas.daniel@intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -4 364/364 360/364
ILK +1-6 365/366 360/366
SNB 450/450 450/450
IVB 498/498 498/498
BYT 289/289 289/289
HSW 564/564 564/564
BDW 417/417 417/417
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt_gem_concurrent_blit_gpuX-bcs-early-read PASS(2, M25) NO_RESULT(1, M25)
*PNV igt_gem_concurrent_blit_prw-bcs-overwrite-source-interruptible PASS(2, M25) NO_RESULT(1, M25)
*PNV igt_gem_userptr_blits_coherency-sync PASS(2, M25) NO_RESULT(1, M25)
*PNV igt_kms_sysfs_edid_timing PASS(3, M25M7) FAIL(1, M25)
*ILK igt_kms_flip_rcs-flip-vs-panning-interruptible PASS(3, M26) DMESG_WARN(1, M26)
*ILK igt_kms_render_direct-render PASS(3, M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_bcs-flip-vs-modeset-interruptible DMESG_WARN(1, M26)PASS(6, M26) DMESG_WARN(1, M26)
*ILK igt_kms_flip_blocking-absolute-wf_vblank-interruptible NSPT(1, M26)PASS(2, M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_busy-flip-interruptible DMESG_WARN(1, M26)PASS(5, M26) DMESG_WARN(1, M26)
*ILK igt_kms_flip_rcs-flip-vs-dpms PASS(4, M26) DMESG_WARN(1, M26)
ILK igt_kms_flip_wf_vblank-ts-check DMESG_WARN(2, M26)PASS(11, M26M37) PASS(1, M26)
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
prev parent reply other threads:[~2014-12-03 1:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 11:12 [PATCH] drm/i915: Don't pin LRC in GGTT when dumping in debugfs Thomas Daniel
2014-11-20 11:16 ` Chris Wilson
2014-11-20 11:25 ` Daniel, Thomas
2014-11-20 11:39 ` Daniel Vetter
2014-11-20 11:41 ` Chris Wilson
2014-11-20 12:09 ` Daniel, Thomas
2014-11-20 12:28 ` Chris Wilson
2014-11-20 12:50 ` Daniel Vetter
2014-11-25 14:30 ` Daniel, Thomas
2014-11-25 14:44 ` Chris Wilson
2014-11-25 15:59 ` Daniel Vetter
2014-11-25 16:42 ` Daniel, Thomas
2014-11-25 20:51 ` Chris Wilson
2014-11-26 12:28 ` Daniel Vetter
2014-12-02 13:21 ` Thomas Daniel
2014-12-02 14:22 ` Daniel Vetter
2014-12-03 1:39 ` shuang.he [this message]
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='84c8a8$id1bro@orsmga001.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.daniel@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