From: shuang.he@intel.com
To: shuang.he@intel.com, ethan.gao@intel.com,
intel-gfx@lists.freedesktop.org, yu.dai@intel.com
Subject: Re: [PATCH v2 18/18] Documentation/drm: kerneldoc for GuC
Date: 09 Apr 2015 06:24:01 -0700 [thread overview]
Message-ID: <acb6cf$l1g6ae@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1428084524-28437-19-git-send-email-yu.dai@intel.com>
Tested-By: Intel Graphics QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
Task id: 6129
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV -1 276/276 275/276
ILK -2 302/302 300/302
SNB -1 313/313 312/313
IVB -1 337/337 336/337
BYT -1 286/286 285/286
HSW -1 395/395 394/395
BDW -3 321/321 318/321
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*PNV igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*ILK igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*ILK igt@gem_fenced_exec_thrash@no-spare-fences-busy PASS(3) DMESG_WARN(1)
(dmesg patch applied)drm:i915_hangcheck_elapsed[i915]]*ERROR*Hangcheck_timer_elapsed...bsd_ring_idle@Hangcheck timer elapsed... bsd ring idle
*SNB igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*IVB igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*BYT igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*HSW igt@drv_debugfs_reader PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:trying_to_register_non-static_key@INFO: trying to register non-static key.
*BDW igt@drm_vma_limiter PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:possible_circular_locking_dependency_detected@INFO: possible circular locking dependency detected
*BDW igt@gem_dummy_reloc_loop@render PASS(3) DMESG_WARN(1)
(dmesg patch applied)drm:i915_hangcheck_elapsed[i915]]*ERROR*Hangcheck_timer_elapsed...render_ring_idle@Hangcheck timer elapsed... render ring idle
*BDW igt@gem_exec_faulting_reloc@no-prefault PASS(3) DMESG_WARN(1)
(dmesg patch applied)INFO:possible_circular_locking_dependency_detected@INFO: possible circular locking dependency detected
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-04-09 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 18:08 [PATCH v2 00/18] *** Command submission via GuC for SKL *** yu.dai
2015-04-03 18:08 ` [PATCH v2 01/18] drm/i915: Add guc firmware interface headers yu.dai
2015-04-03 18:08 ` [PATCH v2 02/18] drm/i915: Add i915_gem_object_write() to i915_gem.c yu.dai
2015-04-03 18:08 ` [PATCH v2 03/18] drm/i915: Unified firmware loading mechanism yu.dai
2015-04-03 18:08 ` [PATCH v2 04/18] drm/i915: GuC firmware loader yu.dai
2015-04-03 18:08 ` [PATCH v2 05/18] drm/i915: Add firmware version check yu.dai
2015-04-03 18:08 ` [PATCH v2 06/18] drm/i915: Defer default hardware context initialisation until first open yu.dai
2015-04-03 18:08 ` [PATCH v2 07/18] drm/i915: Move execlists defines from .c to .h yu.dai
2015-04-03 18:08 ` [PATCH v2 08/18] drm/i915: Make several execlist helper functions external yu.dai
2015-04-03 18:08 ` [PATCH v2 09/18] drm/i915: Add functions to allocate / release gem obj for GuC yu.dai
2015-04-03 18:08 ` [PATCH v2 10/18] drm/i915: Functions to support command submission via GuC yu.dai
2015-04-03 18:08 ` [PATCH v2 11/18] drm/i915: Integration of GuC client yu.dai
2015-04-03 18:08 ` [PATCH v2 12/18] drm/i915: Interrupt routing for GuC scheduler yu.dai
2015-04-03 18:08 ` [PATCH v2 13/18] drm/i915: Enable commands submission via GuC yu.dai
2015-04-03 18:08 ` [PATCH v2 14/18] drm/i915: debugfs of GuC status yu.dai
2015-04-03 18:08 ` [PATCH v2 15/18] drm/i915: Enable GuC firmware log yu.dai
2015-04-03 18:08 ` [PATCH v2 16/18] drm/i915: Ring Context allocating for GuC yu.dai
2015-04-03 18:08 ` [PATCH v2 17/18] drm/i915: Taking forcewake during GuC load yu.dai
2015-04-03 18:08 ` [PATCH v2 18/18] Documentation/drm: kerneldoc for GuC yu.dai
2015-04-09 13:24 ` shuang.he [this message]
2015-04-09 13:28 ` 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='acb6cf$l1g6ae@fmsmga002.fm.intel.com' \
--to=shuang.he@intel.com \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yu.dai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.