From: shuang.he@intel.com
To: shuang.he@intel.com, intel-gfx@lists.freedesktop.org,
kenneth@whitecape.org
Subject: Re: [PATCH] drm/i915: Make sample_c messages go faster on Haswell.
Date: 04 Jan 2015 16:48:23 -0800 [thread overview]
Message-ID: <71e320$f3rp89@orsmga003.jf.intel.com> (raw)
In-Reply-To: <1420071780-1075-1-git-send-email-kenneth@whitecape.org>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 363/364 363/364
ILK -1 364/366 363/366
SNB +2-1 443/450 444/450
IVB 496/498 496/498
BYT 288/289 288/289
HSW +2-6 542/564 538/564
BDW 415/417 415/417
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*ILK igt_gem_fenced_exec_thrash_no-spare-fences-busy PASS(2, M37) DMESG_WARN(1, M37)
*SNB igt_kms_flip_modeset-vs-vblank-race DMESG_WARN(2, M35) PASS(1, M35)
SNB igt_kms_flip_modeset-vs-vblank-race-interruptible DMESG_WARN(2, M35M22)PASS(1, M35) DMESG_WARN(1, M35)
SNB igt_kms_plane_plane-position-hole-pipe-B-plane-1 DMESG_WARN(1, M35)PASS(2, M35M22) PASS(1, M35)
*HSW igt_kms_flip_flip-vs-expired-vblank PASS(2, M40) DMESG_WARN(1, M40)
*HSW igt_kms_flip_flip-vs-expired-vblank-interruptible PASS(2, M40) DMESG_WARN(1, M40)
*HSW igt_kms_flip_nonexisting-fb PASS(2, M40) DMESG_WARN(1, M40)
*HSW igt_kms_flip_nonexisting-fb-interruptible PASS(2, M40) DMESG_WARN(1, M40)
*HSW igt_kms_flip_single-buffer-flip-vs-dpms-off-vs-modeset PASS(3, M40M19) DMESG_WARN(1, M40)
*HSW igt_kms_plane_plane-panning-bottom-right-pipe-C-plane-1 TIMEOUT(2, M40)PASS(1, M19) PASS(1, M40)
*HSW igt_kms_plane_plane-position-hole-pipe-A-plane-2 PASS(2, M40) DMESG_WARN(1, M40)
HSW igt_pm_rpm_modeset-non-lpsp-stress-no-wait NSPT(1, M19)DMESG_WARN(1, M40)PASS(1, M40) PASS(1, M40)
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-01-05 0:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:23 [PATCH] drm/i915: Make sample_c messages go faster on Haswell Kenneth Graunke
2015-01-05 0:48 ` shuang.he [this message]
2015-01-05 13:19 ` Daniel Vetter
2015-01-05 21:39 ` Kenneth Graunke
2015-01-06 5:11 ` Xiang, Haihao
2015-01-06 5:54 ` Kenneth Graunke
2015-01-06 6:39 ` Xiang, Haihao
2015-01-06 7:00 ` [Intel-gfx] " Xiang, Haihao
2015-01-06 7:03 ` Kenneth Graunke
2015-01-06 7:15 ` [Intel-gfx] " Xiang, Haihao
2015-01-06 8:08 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-10-29 22:12 Kenneth Graunke
2014-10-30 8:50 ` Ville Syrjälä
2014-10-30 9:00 ` Ville Syrjälä
2014-10-30 9:32 ` Kenneth Graunke
2014-10-30 11:01 ` Ville Syrjälä
2014-10-30 17:32 ` Kenneth Graunke
2014-10-30 19:26 ` Ville Syrjälä
2014-10-30 19:57 ` Kenneth Graunke
2014-10-31 9:27 ` Ville Syrjälä
2014-10-31 9:43 ` Jani Nikula
2014-11-03 12:48 ` Daniel Vetter
2014-11-03 16:15 ` Dave Gordon
2014-11-07 18:46 ` Matt Turner
2014-11-11 10:16 ` Daniel Vetter
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='71e320$f3rp89@orsmga003.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox