From: Damien Lespiau <damien.lespiau@intel.com>
To: shuang.he@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915/skl: Read out crtl1 for eDP/DPLL0
Date: Sat, 15 Nov 2014 10:54:47 +0000 [thread overview]
Message-ID: <20141115105447.GA14746@strange.ger.corp.intel.com> (raw)
In-Reply-To: <84c8a8$i41s53@orsmga001.jf.intel.com>
Hi Shuang,
You wanted suggestions, so how about:
For both examples, to determine the size of the column, I'd take the
length of the longest value of that column (including the title) and add
4 to account for spacing. Left alignment for text, right alignement for
numbers (of course, all of that is debatable).
On Fri, Nov 14, 2014 at 09:28:03PM -0800, shuang.he@intel.com wrote:
> Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
> -------------------------------------Summary-------------------------------------
> Platform: baseline_drm_intel_nightly_pass_rate->patch_applied_pass_rate
> BYT: pass/total=290/291->290/291
> PNV: pass/total=352/356->356/356
> ILK: pass/total=371/372->364/372
> IVB: pass/total=545/546->545/546
> SNB: pass/total=424/425->424/425
> HSW: pass/total=579/579->579/579
> BDW: pass/total=434/435->434/435
For this one:
- a bit more spacing
- some table-like alignment. That's assuming the mail client will use
monospaced fonts for text emails, it really should.
- add the delta so it's easier to parse the interesting information
- sort by gens
- baseline_drm_intel_nightly_pass_rate can really just be
drm-intel-nightly
- it's not just a single patch applied, so series applied?
Platform Delta drm-intel-nightly Series Applied
--------------------------------------------------------
PNV +4 352/356 356/356
ILK -7 371/372 364/372
SNB 0 424/425 424/425
IVB 0 545/546 545/546
BYT 0 290/291 290/291
HSW 0 579/579 579/579
BDW 0 434/435 434/435
> -------------------------------------Detailed-------------------------------------
> test_platform: test_suite, test_case, result_with_drm_intel_nightly(count, machine_id...)...->result_with_patch_applied(count, machine_id)...
> PNV: Intel_gpu_tools, igt_gen3_mixed_blits, DMESG_WARN(1, M23) -> PASS(4, M7)
> PNV: Intel_gpu_tools, igt_gen3_render_mixed_blits, CRASH(1, M23) -> PASS(1, M7)
> PNV: Intel_gpu_tools, igt_gen3_render_tiledx_blits, CRASH(1, M23) -> PASS(1, M7)
> PNV: Intel_gpu_tools, igt_gen3_render_tiledy_blits, CRASH(1, M23) -> PASS(1, M7)
> ILK: Intel_gpu_tools, igt_kms_flip_flip-vs-absolute-wf_vblank, DMESG_WARN(1, M26)PASS(3, M37M26) -> DMESG_WARN(2, M26)PASS(2, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_flip-vs-absolute-wf_vblank-interruptible, DMESG_WARN(1, M26)PASS(3, M37M26) -> DMESG_WARN(1, M26)PASS(3, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_flip-vs-modeset-vs-hang-interruptible, PASS(4, M37M26) -> NSPT(1, M26)PASS(3, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_flip-vs-wf_vblank-interruptible, DMESG_WARN(1, M26)PASS(3, M37M26) -> DMESG_WARN(1, M26)PASS(3, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_plain-flip, PASS(4, M37M26) -> DMESG_WARN(2, M26)PASS(2, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_plain-flip-interruptible, PASS(4, M37M26) -> DMESG_WARN(2, M26)PASS(2, M26)
> ILK: Intel_gpu_tools, igt_kms_flip_rcs-flip-vs-modeset-interruptible, PASS(4, M37M26) -> DMESG_WARN(1, M26)PASS(3, M26)
And for this one:
- it's not nessary to repeat the test suite name for every single row,
if needed at all (I don't think it is when replying to kernel
patches), it can be put beforehand.
- sorted by gen
- The machine id isn't useful in this report
- It'd be nice to add a some explanations on how to decipher the
result column (what is the count, what the various states mean).
Maybe after the table as it only needs to be read a few times to get
it.
Platform Test drm-intel-nightly Series Applied
-------------------------------------------------------------------------------------------------------------------
ILK igt_kms_flip_flip-vs-absolute-wf_vblank DMESG_WARN(1) PASS(3) DMESG_WARN(2) PASS(2)
ILK igt_kms_flip_flip-vs-absolute-wf_vblank-interruptible DMESG_WARN(1) PASS(3) DMESG_WARN(1) PASS(3)
..
HTH,
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-15 10:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 17:24 [PATCH 0/4] SKL eDP clocks Damien Lespiau
2014-11-14 17:24 ` [PATCH 1/4] drm/i915/skl: Remove spurious warn in get_ddi_pll() Damien Lespiau
2014-11-17 12:40 ` Paulo Zanoni
2014-11-14 17:24 ` [PATCH 2/4] drm/i915/skl: Set the eDP link rate on DPLL0 Damien Lespiau
2014-11-17 18:24 ` Daniel Vetter
2014-11-14 17:24 ` [PATCH 3/4] drm/i915/skl: Use the pipe config DPLL tracking to query the link clock Damien Lespiau
2014-11-14 17:24 ` [PATCH 4/4] drm/i915/skl: Read out crtl1 for eDP/DPLL0 Damien Lespiau
2014-11-15 5:28 ` shuang.he
2014-11-15 10:54 ` Damien Lespiau [this message]
2014-11-17 15:03 ` Daniel Vetter
2014-11-18 8:14 ` He, Shuang
2014-11-18 8:11 ` He, Shuang
2014-11-17 18:28 ` Daniel Vetter
2014-11-18 8:18 ` Daniel Vetter
2014-11-21 16:00 ` [PATCH v2] " Damien Lespiau
2014-11-21 16:14 ` [PATCH v3] " Damien Lespiau
2014-11-21 17:46 ` Daniel Vetter
2014-11-17 17:04 ` [PATCH 0/4] SKL eDP clocks Paulo Zanoni
2014-11-17 17:08 ` Damien Lespiau
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=20141115105447.GA14746@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shuang.he@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