Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for GuC submission functions/struct name/prototype update

Quoting Patchwork (2017-11-13 09:23:47) > == Series Details == > > Series: GuC submission functions/struct name/prototype update > URL : https://patchwork.freedesktop.org/series/33679/ > State : failure > > == Summary == > > Series 33679v1 GuC submission functions/struct name/prototype update

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: This set enables 90/270 degree rotation on 16bpp planes on gen10 (rev2)

== Series Details == Series: drm/i915: This set enables 90/270 degree rotation on 16bpp planes on gen10 (rev2) URL : https://patchwork.freedesktop.org/series/33133/ State : success == Summary == Warning: bzip CI_DRM_3343/shard-glkb6/results34.json.bz2 wasn't in correct JSON format Test

[Intel-gfx] [PATCH] drm/i915/glk: Apply WaProgramL3SqcReg1DefaultForPerf for GLK too

Testing the texture read performance shows that the same tuning for the SQ credits is needed on GLK as on BXT/APL. This has been also confirmed by Altug from the HW team. Cc: Altug Koker Signed-off-by: Valtteri Rantala ---

Re: [Intel-gfx] [PATCH 3/4] drm/i915/guc: Rename i915_guc_submission.c|h to intel_guc_submission.c|h

On Mon, 13 Nov 2017 09:48:13 +0100, Sagar Arun Kamble wrote: With all component structures and functions named as intel_guc*, change the names of GuC submission source files. There were bunch of style issues in guc_submission.c that are highlighted now by

Re: [Intel-gfx] [PATCH 1/4] drm/i915/guc: Update name and prototype of GuC submission related functions

Quoting Michal Wajdeczko (2017-11-14 12:23:18) > On Mon, 13 Nov 2017 09:48:11 +0100, Sagar Arun Kamble > > -static void i915_guc_submission_unpark(struct intel_engine_cs *engine) > > +static void intel_guc_submission_unpark(struct intel_engine_cs *engine) > > Both park/unpark are also static

Re: [Intel-gfx] [PATCH 2/4] drm/i915/guc: Rename i915_guc_client struct to intel_guc_client

On Mon, 13 Nov 2017 09:48:12 +0100, Sagar Arun Kamble wrote: GuC submission clients are currently being used in kernel only hence update the structure name to intel_guc_client. Signed-off-by: Sagar Arun Kamble Cc: Michal Wajdeczko

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/selftests: Increase size for mock ringbuffer

== Series Details == Series: series starting with [1/3] drm/i915/selftests: Increase size for mock ringbuffer URL : https://patchwork.freedesktop.org/series/33768/ State : success == Summary == Series 33768v1 series starting with [1/3] drm/i915/selftests: Increase size for mock ringbuffer

Re: [Intel-gfx] Tracing PM-triggered GPU frequency changes from user space

Quoting Heinrich Fink (2017-11-14 12:19:28) > Hi, > > is there a simple way for user space to trace PM-triggered changes of > GPU frequency on GEN9/Skylake? What is a PM-triggered change of gpu freq? Do you mean when the hw itself throttles depending on thermal load. Then no. Best you can do is

Re: [Intel-gfx] [PATCH 1/4] drm/i915/guc: Update name and prototype of GuC submission related functions

On Mon, 13 Nov 2017 09:48:11 +0100, Sagar Arun Kamble wrote: i915 GuC submission is hardware interface and GuC APIs that are not user facing should be named intel_guc* hence we change GuC submission related functions name prefix to intel_guc. Also changed the

[Intel-gfx] Tracing PM-triggered GPU frequency changes from user space

Hi, is there a simple way for user space to trace PM-triggered changes of GPU frequency on GEN9/Skylake? i915:intel_gpu_freq_change seems to only report SW-triggered frequency change requests. The best option I currently see is to poll gt_act_freq_mhz, but I was hoping for a more elegant

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: This set enables 90/270 degree rotation on 16bpp planes on gen10 (rev2)

== Series Details == Series: drm/i915: This set enables 90/270 degree rotation on 16bpp planes on gen10 (rev2) URL : https://patchwork.freedesktop.org/series/33133/ State : success == Summary == Series 33133v2 drm/i915: This set enables 90/270 degree rotation on 16bpp planes on gen10

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/2] drm/i915: Object w/o backing storage is banned by -ENXIO

== Series Details == Series: series starting with [CI,1/2] drm/i915: Object w/o backing storage is banned by -ENXIO URL : https://patchwork.freedesktop.org/series/33763/ State : success == Summary == Warning: bzip CI_DRM_3343/shard-glkb6/results34.json.bz2 wasn't in correct JSON format

[Intel-gfx] [PATCH 2/3] drm/i915: Make request's wait-for-space explicit

At the start of building a request, we would wait for roughly enough space to fit the average request (to reduce the likelihood of having to wait and abort partway through request construction). To achieve we would try to begin a 0-length command packet, this just adds extra confusion so make the

Re: [Intel-gfx] [PATCH] drm/i915: Fix function name in comment

On Mon, Nov 13, 2017 at 04:46:38PM -0800, Lucas De Marchi wrote: > Commit 78597996370c (drm/i915/bxt: Fix PPS lost state after suspend > breaking eDP link training) renamed the function to > intel_power_sequencer_reset() but forgot to update comment. > > Cc: Imre Deak >

[Intel-gfx] [PATCH 1/3] drm/i915/selftests: Increase size for mock ringbuffer

We don't actually emit any commands into the ringbuffer, so we set it very small. However, an upcoming change centralises the wait-for-space into i915_gem_request_alloc() and that imposes a minimum size upon all ringbuffers (mock or real) of MIN_SPACE_FOR_ADD_REQUEST. Grow the mock ringbuffer such

[Intel-gfx] [PATCH 3/3] drm/i915: Automatic i915_switch_context for legacy

During request construction, after pinning the context we know whether or not we have to emit a context switch. So move this common operation from every caller into i915_gem_request_alloc() itself. v2: Always submit the request if we emitted some commands during request construction, as typically

Re: [Intel-gfx] [PATCH] ftrace: Allow configuring global trace buffer size (for dump-on-oops)

Quoting Chris Wilson (2017-11-13 13:07:08) > We have recently turned on ftrace-dump-on-oops for i915's CI and an > issue we have encountered is that the trace buffer size greatly exceeds > the pstore capabilities; we get the tail of the oops but not the > introduction. > > Currently the global

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915: Object w/o backing storage is banned by -ENXIO

== Series Details == Series: series starting with [CI,1/2] drm/i915: Object w/o backing storage is banned by -ENXIO URL : https://patchwork.freedesktop.org/series/33763/ State : success == Summary == Series 33763v1 series starting with [CI,1/2] drm/i915: Object w/o backing storage is banned

[Intel-gfx] ✗ Fi.CI.IGT: warning for drm/i915: Initialize audio only when display is present

== Series Details == Series: drm/i915: Initialize audio only when display is present URL : https://patchwork.freedesktop.org/series/33601/ State : warning == Summary == Test kms_flip: Subgroup basic-flip-vs-modeset: dmesg-warn -> PASS (shard-hsw) fdo#102614 Test

[Intel-gfx] [CI 1/2] drm/i915: Object w/o backing storage is banned by -ENXIO

From: Tina Zhang -ENXIO should be returned when operations are banned from changing backing storage of objects without backing storage. v4: - update "Reviewed-by". (Joonas) v3: - separate this patch from "Introduce GEM proxy" patch-set. (Joonas) v2: - update the patch

[Intel-gfx] [CI 2/2] drm/i915: Introduce GEM proxy

From: Tina Zhang GEM proxy is a kind of GEM, whose backing physical memory is pinned and produced by guest VM and is used by host as read only. With GEM proxy, host is able to access guest physical memory through GEM object interface. As GEM proxy is such a special kind of

Re: [Intel-gfx] [PATCH] drm/debugfs: Fix framebuffer debugfs file init

On Tue, 14 Nov 2017, Dave Airlie wrote: > On 14 November 2017 at 09:12, Noralf Trønnes wrote: >> The introduction of: drm/framebuffer: Add framebuffer debugfs file >> broke vgem. That patch assumed that all drivers had initialized the >>

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/debugfs: Fix framebuffer debugfs file init

== Series Details == Series: drm/debugfs: Fix framebuffer debugfs file init URL : https://patchwork.freedesktop.org/series/33747/ State : success == Summary == Test kms_flip: Subgroup plain-flip-ts-check-interruptible: fail -> PASS (shard-hsw) fdo#100368 +1

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Initialize audio only when display is present

== Series Details == Series: drm/i915: Initialize audio only when display is present URL : https://patchwork.freedesktop.org/series/33601/ State : success == Summary == Series 33601v1 drm/i915: Initialize audio only when display is present

<    1   2   3