public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: shuang.he@intel.com
To: shuang.he@intel.com, lei.a.liu@intel.com,
	intel-gfx@lists.freedesktop.org, tvrtko.ursulin@linux.intel.com
Subject: Re: [PATCH v4] drm/i915: Report correct GGTT space usage
Date: 02 Jul 2015 00:30:47 -0700	[thread overview]
Message-ID: <6299f3$mhvo66@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1435674767-6576-1-git-send-email-tvrtko.ursulin@linux.intel.com>

Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6685
-------------------------------------Summary-------------------------------------
Platform          Delta          drm-intel-nightly          Series Applied
ILK                 -1              302/302              301/302
SNB                                  312/316              312/316
IVB                                  343/343              343/343
BYT                 -3              287/287              284/287
HSW                                  380/380              380/380
-------------------------------------Detailed-------------------------------------
Platform  Test                                drm-intel-nightly          Series Applied
*ILK  igt@gem_persistent_relocs@forked-interruptible-thrashing      PASS(1)      DMESG_WARN(1)
(dmesg patch applied)drm:i915_hangcheck_elapsed[i915]]*ERROR*Hangcheck_timer_elapsed...bsd_ring_idle@Hangcheck timer elapsed... bsd ring idle
*BYT  igt@gem_partial_pwrite_pread@reads      PASS(1)      FAIL(1)
*BYT  igt@gem_partial_pwrite_pread@reads-display      PASS(1)      FAIL(1)
*BYT  igt@gem_partial_pwrite_pread@reads-uncached      PASS(1)      FAIL(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

  parent reply	other threads:[~2015-07-02  7:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  9:28 [PATCH] drm/i915: Report correct GGTT space usage Tvrtko Ursulin
2015-06-30  9:36 ` Chris Wilson
2015-06-30  9:50   ` Tvrtko Ursulin
2015-06-30 10:01     ` Chris Wilson
2015-06-30 10:27       ` [PATCH v2] " Tvrtko Ursulin
2015-06-30 10:33         ` Chris Wilson
2015-06-30 11:03           ` Tvrtko Ursulin
2015-06-30 11:35             ` Chris Wilson
2015-06-30 12:53               ` [PATCH v3] " Tvrtko Ursulin
2015-06-30 13:30                 ` Chris Wilson
2015-06-30 14:32                   ` [PATCH v4] " Tvrtko Ursulin
2015-06-30 15:00                     ` Chris Wilson
2015-07-01 10:53                       ` Tvrtko Ursulin
2015-07-01 10:58                         ` Chris Wilson
2015-07-02  7:30                     ` shuang.he [this message]
2015-07-02  0:23                 ` [PATCH v3] " shuang.he
2015-07-01 20:01         ` [PATCH v2] " shuang.he
2015-07-01 17:58 ` [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='6299f3$mhvo66@orsmga002.jf.intel.com' \
    --to=shuang.he@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lei.a.liu@intel.com \
    --cc=tvrtko.ursulin@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