* [PATCH] drm/i915/guc: Log significant events at the info level
@ 2017-02-06 11:32 Tvrtko Ursulin
2017-02-06 11:44 ` Chris Wilson
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Tvrtko Ursulin @ 2017-02-06 11:32 UTC (permalink / raw)
To: Intel-gfx
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Currently to establish whether GuC firmware has been loaded or
submission enabled (default DRM log level), one has to detect
the absence of the message saying that the load has been skipped
and infer the opposite.
It is better to log the fact GuC firmware has been loaded and/or
submission enabled explicitly to avoid any guesswork when looking
at the logs.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/i915/intel_guc_loader.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
index 2f1cf9aea04e..ccf55d6a164e 100644
--- a/drivers/gpu/drm/i915/intel_guc_loader.c
+++ b/drivers/gpu/drm/i915/intel_guc_loader.c
@@ -520,10 +520,6 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
guc_fw->load_status = INTEL_UC_FIRMWARE_SUCCESS;
- DRM_DEBUG_DRIVER("GuC fw status: fetch %s, load %s\n",
- intel_uc_fw_status_repr(guc_fw->fetch_status),
- intel_uc_fw_status_repr(guc_fw->load_status));
-
intel_guc_auth_huc(dev_priv);
if (i915.enable_guc_submission) {
@@ -536,6 +532,11 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
guc_interrupts_capture(dev_priv);
}
+ DRM_INFO("GuC %s (firmware %s [%u.%u])\n",
+ i915.enable_guc_submission ? "submission enabled" : "loaded",
+ guc_fw->path,
+ guc_fw->major_ver_wanted, guc_fw->minor_ver_wanted);
+
return 0;
fail:
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/guc: Log significant events at the info level
2017-02-06 11:32 [PATCH] drm/i915/guc: Log significant events at the info level Tvrtko Ursulin
@ 2017-02-06 11:44 ` Chris Wilson
2017-02-06 11:51 ` Michal Wajdeczko
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2017-02-06 11:44 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: Intel-gfx
On Mon, Feb 06, 2017 at 11:32:06AM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Currently to establish whether GuC firmware has been loaded or
> submission enabled (default DRM log level), one has to detect
> the absence of the message saying that the load has been skipped
> and infer the opposite.
>
> It is better to log the fact GuC firmware has been loaded and/or
> submission enabled explicitly to avoid any guesswork when looking
> at the logs.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc_loader.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
> index 2f1cf9aea04e..ccf55d6a164e 100644
> --- a/drivers/gpu/drm/i915/intel_guc_loader.c
> +++ b/drivers/gpu/drm/i915/intel_guc_loader.c
> @@ -520,10 +520,6 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
>
> guc_fw->load_status = INTEL_UC_FIRMWARE_SUCCESS;
>
> - DRM_DEBUG_DRIVER("GuC fw status: fetch %s, load %s\n",
> - intel_uc_fw_status_repr(guc_fw->fetch_status),
> - intel_uc_fw_status_repr(guc_fw->load_status));
> -
> intel_guc_auth_huc(dev_priv);
>
> if (i915.enable_guc_submission) {
> @@ -536,6 +532,11 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
> guc_interrupts_capture(dev_priv);
> }
>
> + DRM_INFO("GuC %s (firmware %s [%u.%u])\n",
> + i915.enable_guc_submission ? "submission enabled" : "loaded",
> + guc_fw->path,
> + guc_fw->major_ver_wanted, guc_fw->minor_ver_wanted);
I can see that you've considered that this will now be consumed by
users and have made the language more understandable. I think you need
to explain what the numbers are, i.e. "[version %u.%u]".
Other than that, looks good, we don't confuse the user when guc isn't
being used (so that don't start trying to fix it and probably breaking
their system in the process! ;),
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
We are missing the guc version in the error state, if you are feeling on
a roll...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/guc: Log significant events at the info level
2017-02-06 11:32 [PATCH] drm/i915/guc: Log significant events at the info level Tvrtko Ursulin
2017-02-06 11:44 ` Chris Wilson
@ 2017-02-06 11:51 ` Michal Wajdeczko
2017-02-07 8:50 ` [PATCH v2] " Tvrtko Ursulin
2017-02-06 16:22 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-02-07 9:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2) Patchwork
3 siblings, 1 reply; 8+ messages in thread
From: Michal Wajdeczko @ 2017-02-06 11:51 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: Intel-gfx
On Mon, Feb 06, 2017 at 11:32:06AM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Currently to establish whether GuC firmware has been loaded or
> submission enabled (default DRM log level), one has to detect
> the absence of the message saying that the load has been skipped
> and infer the opposite.
>
> It is better to log the fact GuC firmware has been loaded and/or
> submission enabled explicitly to avoid any guesswork when looking
> at the logs.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc_loader.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
> index 2f1cf9aea04e..ccf55d6a164e 100644
> --- a/drivers/gpu/drm/i915/intel_guc_loader.c
> +++ b/drivers/gpu/drm/i915/intel_guc_loader.c
> @@ -520,10 +520,6 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
>
> guc_fw->load_status = INTEL_UC_FIRMWARE_SUCCESS;
>
> - DRM_DEBUG_DRIVER("GuC fw status: fetch %s, load %s\n",
> - intel_uc_fw_status_repr(guc_fw->fetch_status),
> - intel_uc_fw_status_repr(guc_fw->load_status));
> -
> intel_guc_auth_huc(dev_priv);
>
> if (i915.enable_guc_submission) {
> @@ -536,6 +532,11 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
> guc_interrupts_capture(dev_priv);
> }
>
> + DRM_INFO("GuC %s (firmware %s [%u.%u])\n",
> + i915.enable_guc_submission ? "submission enabled" : "loaded",
> + guc_fw->path,
> + guc_fw->major_ver_wanted, guc_fw->minor_ver_wanted);
While with today code it is hard to load fw with different version than 'wanted'
(due to filename schema) but maybe we should still report ver_found here?
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Regards,
Michal
> +
> return 0;
>
> fail:
> --
> 2.7.4
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* ✗ Fi.CI.BAT: failure for drm/i915/guc: Log significant events at the info level
2017-02-06 11:32 [PATCH] drm/i915/guc: Log significant events at the info level Tvrtko Ursulin
2017-02-06 11:44 ` Chris Wilson
2017-02-06 11:51 ` Michal Wajdeczko
@ 2017-02-06 16:22 ` Patchwork
2017-02-07 9:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2) Patchwork
3 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2017-02-06 16:22 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/guc: Log significant events at the info level
URL : https://patchwork.freedesktop.org/series/19158/
State : failure
== Summary ==
Series 19158v1 drm/i915/guc: Log significant events at the info level
https://patchwork.freedesktop.org/api/1.0/series/19158/revisions/1/mbox/
Test drv_hangman:
Subgroup error-state-basic:
pass -> TIMEOUT (fi-hsw-4770)
Test drv_module_reload:
Subgroup basic-no-display:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-reload:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-reload-final:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-reload-inject:
pass -> INCOMPLETE (fi-hsw-4770)
Test gvt_basic:
Subgroup invalid-placeholder-test:
skip -> INCOMPLETE (fi-hsw-4770)
Test kms_busy:
Subgroup basic-flip-default-b:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-default-c:
pass -> INCOMPLETE (fi-hsw-4770)
Test kms_cursor_legacy:
Subgroup basic-busy-flip-before-cursor-atomic:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-busy-flip-before-cursor-legacy:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-after-cursor-atomic:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-after-cursor-legacy:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-after-cursor-varying-size:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-before-cursor-atomic:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-before-cursor-legacy:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-before-cursor-varying-size:
pass -> INCOMPLETE (fi-hsw-4770)
Test kms_flip:
Subgroup basic-flip-vs-dpms:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-vs-modeset:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-flip-vs-wf_vblank:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup basic-plain-flip:
pass -> INCOMPLETE (fi-hsw-4770)
Test kms_force_connector_basic:
Subgroup force-connector-state:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup force-edid:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup force-load-detect:
skip -> INCOMPLETE (fi-hsw-4770)
Subgroup prune-stale-modes:
skip -> INCOMPLETE (fi-hsw-4770)
Test kms_frontbuffer_tracking:
Subgroup basic:
pass -> INCOMPLETE (fi-hsw-4770)
Test kms_pipe_crc_basic:
Subgroup bad-nb-words-1:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup bad-nb-words-3:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup bad-pipe:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup bad-source:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup hang-read-crc-pipe-a:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup hang-read-crc-pipe-b:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup hang-read-crc-pipe-c:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-a:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-a-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-b:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-b-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-c:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup nonblocking-crc-pipe-c-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-a:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-a-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-b:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-b-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-c:
pass -> INCOMPLETE (fi-hsw-4770)
Subgroup read-crc-pipe-c-frame-sequence:
pass -> INCOMPLETE (fi-hsw-4770)
WARNING: Long output truncated
0a3c88ae096a1bdf9a2487a7c24f863528a9269a drm-tip: 2017y-02m-06d-15h-16m-48s UTC integration manifest
d868662 drm/i915/guc: Log significant events at the info level
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3710/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH v2] drm/i915/guc: Log significant events at the info level
2017-02-06 11:51 ` Michal Wajdeczko
@ 2017-02-07 8:50 ` Tvrtko Ursulin
2017-02-07 9:00 ` Chris Wilson
0 siblings, 1 reply; 8+ messages in thread
From: Tvrtko Ursulin @ 2017-02-07 8:50 UTC (permalink / raw)
To: Intel-gfx
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Currently to establish whether GuC firmware has been loaded or
submission enabled (default DRM log level), one has to detect
the absence of the message saying that the load has been skipped
and infer the opposite.
It is better to log the fact GuC firmware has been loaded and/or
submission enabled explicitly to avoid any guesswork when looking
at the logs.
v2:
* Log message polish. (Chris)
* Future proof by reporting found firmware version. (Michal)
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> (v1)
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com> (v1)
---
drivers/gpu/drm/i915/intel_guc_loader.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
index 2f1cf9aea04e..8ef33d88d5a0 100644
--- a/drivers/gpu/drm/i915/intel_guc_loader.c
+++ b/drivers/gpu/drm/i915/intel_guc_loader.c
@@ -520,10 +520,6 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
guc_fw->load_status = INTEL_UC_FIRMWARE_SUCCESS;
- DRM_DEBUG_DRIVER("GuC fw status: fetch %s, load %s\n",
- intel_uc_fw_status_repr(guc_fw->fetch_status),
- intel_uc_fw_status_repr(guc_fw->load_status));
-
intel_guc_auth_huc(dev_priv);
if (i915.enable_guc_submission) {
@@ -536,6 +532,11 @@ int intel_guc_setup(struct drm_i915_private *dev_priv)
guc_interrupts_capture(dev_priv);
}
+ DRM_INFO("GuC %s (firmware %s [version %u.%u])\n",
+ i915.enable_guc_submission ? "submission enabled" : "loaded",
+ guc_fw->path,
+ guc_fw->major_ver_found, guc_fw->minor_ver_found);
+
return 0;
fail:
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH v2] drm/i915/guc: Log significant events at the info level
2017-02-07 8:50 ` [PATCH v2] " Tvrtko Ursulin
@ 2017-02-07 9:00 ` Chris Wilson
0 siblings, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2017-02-07 9:00 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: Intel-gfx
On Tue, Feb 07, 2017 at 08:50:25AM +0000, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Currently to establish whether GuC firmware has been loaded or
> submission enabled (default DRM log level), one has to detect
> the absence of the message saying that the load has been skipped
> and infer the opposite.
>
> It is better to log the fact GuC firmware has been loaded and/or
> submission enabled explicitly to avoid any guesswork when looking
> at the logs.
>
> v2:
> * Log message polish. (Chris)
> * Future proof by reporting found firmware version. (Michal)
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> (v1)
> Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com> (v1)
s/v1//
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2)
2017-02-06 11:32 [PATCH] drm/i915/guc: Log significant events at the info level Tvrtko Ursulin
` (2 preceding siblings ...)
2017-02-06 16:22 ` ✗ Fi.CI.BAT: failure for " Patchwork
@ 2017-02-07 9:23 ` Patchwork
2017-02-08 16:03 ` Tvrtko Ursulin
3 siblings, 1 reply; 8+ messages in thread
From: Patchwork @ 2017-02-07 9:23 UTC (permalink / raw)
To: Tvrtko Ursulin; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/guc: Log significant events at the info level (rev2)
URL : https://patchwork.freedesktop.org/series/19158/
State : success
== Summary ==
Series 19158v2 drm/i915/guc: Log significant events at the info level
https://patchwork.freedesktop.org/api/1.0/series/19158/revisions/2/mbox/
Test kms_pipe_crc_basic:
Subgroup nonblocking-crc-pipe-b:
dmesg-warn -> PASS (fi-snb-2520m)
fi-bdw-5557u total:252 pass:238 dwarn:0 dfail:0 fail:0 skip:14
fi-bsw-n3050 total:252 pass:213 dwarn:0 dfail:0 fail:0 skip:39
fi-bxt-j4205 total:252 pass:230 dwarn:0 dfail:0 fail:0 skip:22
fi-bxt-t5700 total:83 pass:70 dwarn:0 dfail:0 fail:0 skip:12
fi-byt-j1900 total:252 pass:225 dwarn:0 dfail:0 fail:0 skip:27
fi-byt-n2820 total:252 pass:221 dwarn:0 dfail:0 fail:0 skip:31
fi-hsw-4770 total:252 pass:233 dwarn:0 dfail:0 fail:0 skip:19
fi-hsw-4770r total:252 pass:233 dwarn:0 dfail:0 fail:0 skip:19
fi-ilk-650 total:252 pass:199 dwarn:0 dfail:0 fail:0 skip:53
fi-ivb-3520m total:252 pass:231 dwarn:0 dfail:0 fail:0 skip:21
fi-ivb-3770 total:252 pass:231 dwarn:0 dfail:0 fail:0 skip:21
fi-kbl-7500u total:252 pass:229 dwarn:0 dfail:0 fail:2 skip:21
fi-skl-6260u total:252 pass:239 dwarn:0 dfail:0 fail:0 skip:13
fi-skl-6700hq total:252 pass:232 dwarn:0 dfail:0 fail:0 skip:20
fi-skl-6700k total:252 pass:227 dwarn:4 dfail:0 fail:0 skip:21
fi-skl-6770hq total:252 pass:239 dwarn:0 dfail:0 fail:0 skip:13
fi-snb-2520m total:252 pass:221 dwarn:0 dfail:0 fail:0 skip:31
fi-snb-2600 total:252 pass:220 dwarn:0 dfail:0 fail:0 skip:32
4b60513d8a00fc960a2d837fcccf6a63c861d9ec drm-tip: 2017y-02m-06d-22h-40m-55s UTC integration manifest
3c26a59 drm/i915/guc: Log significant events at the info level
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3717/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2)
2017-02-07 9:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2) Patchwork
@ 2017-02-08 16:03 ` Tvrtko Ursulin
0 siblings, 0 replies; 8+ messages in thread
From: Tvrtko Ursulin @ 2017-02-08 16:03 UTC (permalink / raw)
To: intel-gfx, Tvrtko Ursulin
On 07/02/2017 09:23, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Log significant events at the info level (rev2)
> URL : https://patchwork.freedesktop.org/series/19158/
> State : success
>
> == Summary ==
>
> Series 19158v2 drm/i915/guc: Log significant events at the info level
> https://patchwork.freedesktop.org/api/1.0/series/19158/revisions/2/mbox/
>
> Test kms_pipe_crc_basic:
> Subgroup nonblocking-crc-pipe-b:
> dmesg-warn -> PASS (fi-snb-2520m)
>
> fi-bdw-5557u total:252 pass:238 dwarn:0 dfail:0 fail:0 skip:14
> fi-bsw-n3050 total:252 pass:213 dwarn:0 dfail:0 fail:0 skip:39
> fi-bxt-j4205 total:252 pass:230 dwarn:0 dfail:0 fail:0 skip:22
> fi-bxt-t5700 total:83 pass:70 dwarn:0 dfail:0 fail:0 skip:12
> fi-byt-j1900 total:252 pass:225 dwarn:0 dfail:0 fail:0 skip:27
> fi-byt-n2820 total:252 pass:221 dwarn:0 dfail:0 fail:0 skip:31
> fi-hsw-4770 total:252 pass:233 dwarn:0 dfail:0 fail:0 skip:19
> fi-hsw-4770r total:252 pass:233 dwarn:0 dfail:0 fail:0 skip:19
> fi-ilk-650 total:252 pass:199 dwarn:0 dfail:0 fail:0 skip:53
> fi-ivb-3520m total:252 pass:231 dwarn:0 dfail:0 fail:0 skip:21
> fi-ivb-3770 total:252 pass:231 dwarn:0 dfail:0 fail:0 skip:21
> fi-kbl-7500u total:252 pass:229 dwarn:0 dfail:0 fail:2 skip:21
> fi-skl-6260u total:252 pass:239 dwarn:0 dfail:0 fail:0 skip:13
> fi-skl-6700hq total:252 pass:232 dwarn:0 dfail:0 fail:0 skip:20
> fi-skl-6700k total:252 pass:227 dwarn:4 dfail:0 fail:0 skip:21
> fi-skl-6770hq total:252 pass:239 dwarn:0 dfail:0 fail:0 skip:13
> fi-snb-2520m total:252 pass:221 dwarn:0 dfail:0 fail:0 skip:31
> fi-snb-2600 total:252 pass:220 dwarn:0 dfail:0 fail:0 skip:32
>
> 4b60513d8a00fc960a2d837fcccf6a63c861d9ec drm-tip: 2017y-02m-06d-22h-40m-55s UTC integration manifest
> 3c26a59 drm/i915/guc: Log significant events at the info level
Pushed, thanks for the review.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-02-08 16:03 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-06 11:32 [PATCH] drm/i915/guc: Log significant events at the info level Tvrtko Ursulin
2017-02-06 11:44 ` Chris Wilson
2017-02-06 11:51 ` Michal Wajdeczko
2017-02-07 8:50 ` [PATCH v2] " Tvrtko Ursulin
2017-02-07 9:00 ` Chris Wilson
2017-02-06 16:22 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-02-07 9:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Log significant events at the info level (rev2) Patchwork
2017-02-08 16:03 ` Tvrtko Ursulin
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.