From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 4/4] drm/i915: Use intel_gpu_freq() and intel_freq_opcode()
Date: 27 Jan 2015 16:39:03 -0800 [thread overview]
Message-ID: <84c8a8$j5o8uc@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1422039866-11572-5-git-send-email-ville.syrjala@linux.intel.com>
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 5641
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -1 353/353 352/353
ILK 353/353 353/353
SNB +1-1 400/422 400/422
IVB +2-1 485/487 486/487
BYT 296/296 296/296
HSW +1-1 507/508 507/508
BDW 401/402 401/402
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt_gen3_render_linear_blits PASS(3, M25M23) CRASH(1, M23)
*SNB igt_kms_flip_event_leak NSPT(3, M35M22) PASS(1, M22)
*SNB igt_kms_flip_tiling_flip-changes-tiling PASS(2, M35M22) FAIL(1, M22)
IVB igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(2, M34)PASS(3, M4) PASS(1, M4)
IVB igt_gem_storedw_batches_loop_normal DMESG_WARN(2, M34M4)PASS(5, M34M4M21) PASS(1, M4)
*IVB igt_gem_storedw_batches_loop_secure-dispatch PASS(2, M34M4) DMESG_WARN(1, M4)
HSW igt_gem_pwrite_pread_snooped-pwrite-blt-cpu_mmap-performance DMESG_WARN(1, M40)PASS(5, M40M20) PASS(1, M20)
HSW igt_gem_storedw_loop_vebox DMESG_WARN(1, M20)PASS(2, M40M20) DMESG_WARN(1, M20)
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:[~2015-01-28 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 19:04 [PATCH 0/4] drm/i915: PMINTRMSK fix for VLV/CHV and some other rps stuff ville.syrjala
2015-01-23 19:04 ` [PATCH 1/4] drm/i915: Update PMINTRMSK on VLV/CHV after sysfs min/max freq change ville.syrjala
2015-01-23 20:51 ` Chris Wilson
2015-01-25 9:31 ` Chris Wilson
2015-01-23 19:04 ` [PATCH 2/4] drm/i915: Add gt_act_freq_mhz sysfs file ville.syrjala
2015-01-25 9:34 ` Chris Wilson
2015-01-26 20:22 ` O'Rourke, Tom
2015-01-26 20:42 ` Chris Wilson
2015-01-27 9:37 ` Ville Syrjälä
2015-01-23 19:04 ` [PATCH 3/4] drm/i915: Add intel_gpu_freq() and intel_freq_opcode() ville.syrjala
2015-01-25 9:34 ` Chris Wilson
2015-01-23 19:04 ` [PATCH 4/4] drm/i915: Use " ville.syrjala
2015-01-25 9:35 ` Chris Wilson
2015-01-28 0: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$j5o8uc@orsmga001.jf.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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