[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset

== Series Details == Series: series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset URL : https://patchwork.freedesktop.org/series/62986/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385_full -> Patchwork_13475_full ===

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: CTS fixes (rev8)

== Series Details == Series: drm/i915: CTS fixes (rev8) URL : https://patchwork.freedesktop.org/series/62437/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385_full -> Patchwork_13474_full Summary --- **SUCCESS**

screen freeze with 5.2-rc6 Dell XPS-13 skylake i915

The symptoms are really weird: the screen image is locked in place. The machine is still functional and if I log in over the network I can do anything I like, including killing the X server and the display will never alter. It also seems that the system is accepting keyboard input because when it

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/guc: Avoid reclaim locks during reset

== Series Details == Series: series starting with [1/2] drm/i915/guc: Avoid reclaim locks during reset URL : https://patchwork.freedesktop.org/series/62973/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385_full -> Patchwork_13473_full ===

Re: [Intel-gfx] [PATCH V2] include: linux: Regularise the use of FIELD_SIZEOF macro

On Sat, 2019-06-29 at 17:25 +0300, Alexey Dobriyan wrote: > On Tue, Jun 11, 2019 at 03:00:10PM -0600, Andreas Dilger wrote: > > On Jun 11, 2019, at 2:48 PM, Andrew Morton > > wrote: > > > On Wed, 12 Jun 2019 01:08:36 +0530 Shyam Saini > > > wrote: > > I did a check, and FIELD_SIZEOF() is used a

Re: [Intel-gfx] [PATCH] drm/kms: Catch mode_object lifetime errors

On Fri, Jun 28, 2019 at 7:24 PM Sean Paul wrote: > > On Fri, Jun 14, 2019 at 08:17:23AM +0200, Daniel Vetter wrote: > > Only dynamic mode objects, i.e. those which are refcounted and have a free > > callback, can be added while the overall drm_device is visible to > > userspace. All others must be

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset

== Series Details == Series: series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset URL : https://patchwork.freedesktop.org/series/62986/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385 -> Patchwork_13475 =

Re: [Intel-gfx] [PATCH] drm/i915: fix whitelist selftests with readonly registers

Ship it! On 29/06/2019 16:13, Chris Wilson wrote: From: Lionel Landwerlin When a register is readonly there is not much we can tell about its value (apart from its default value?). This can be covered by tests exercising the value of the register from userspace. For PS_INVOCATION_COUNT we've

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset

== Series Details == Series: series starting with [1/5] drm/i915/guc: Avoid reclaim locks during reset URL : https://patchwork.freedesktop.org/series/62986/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.5.2 Commit: drm/i915/guc: Avoid reclaim locks during reset

Re: [Intel-gfx] [PATCH i-g-t] tests/i915/gem_ctx_switch: Update with engine discovery

Quoting Tvrtko Ursulin (2019-06-27 11:20:19) > From: Tvrtko Ursulin > > I converted this one as an example, or at least to drive the discussion, > how more complex tests can be converted. > > I have kept the legacy execbuf abi testing prefixed with "legacy-". > > New tests were added to exercis

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: CTS fixes (rev8)

== Series Details == Series: drm/i915: CTS fixes (rev8) URL : https://patchwork.freedesktop.org/series/62437/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385 -> Patchwork_13474 Summary --- **SUCCESS** No regres

[Intel-gfx] [PATCH 4/5] drm/i915/execlists: Refactor CSB state machine

Daniele pointed out that the CSB status information will change with Tigerlake and suggested that we could rearrange our state machine to hide the differences in generation. gcc also prefers the explicit state machine, so make it so: process_csb 19801967 -13

[Intel-gfx] [PATCH 1/5] drm/i915/guc: Avoid reclaim locks during reset

During reset, we must be very selective in which locks we take as most are tainted by being held across a wait or reclaim (kmalloc) which implicitly waits. Inside the guc reset path, we reset the ADS to sane defaults, but must keep it pinned from initialisation to avoid having to pin it during rese

[Intel-gfx] [PATCH 2/5] drm/i915: Markup potential lock for i915_active

Make the lockchains more deterministic via i915_active by flagging the potential lock. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_active.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c index cb6a1eadf

[Intel-gfx] [PATCH 5/5] drm/i915/execlists: Hesitate before slicing

Be a little more hesitant before injecting a timeslice, and try to take into account any change in priority that is due for the running task before switching to another task. This will allow us to arbitrarily prevent switching away from a request if we deem it necessarily to disable preemption, for

[Intel-gfx] [PATCH 3/5] drm/i915: Mark up vma->active as safe for use inside shrinkers

Since a shrinker may be forced to wait on GPU activity, i915_active_wait(&vma->active) must be safe for use inside a shrinker, and so let's mark up the lock as being acquired by the shrinker to avoid any nasty surprises creeping in. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_vma.c

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev8)

== Series Details == Series: drm/i915: CTS fixes (rev8) URL : https://patchwork.freedesktop.org/series/62437/ State : warning == Summary == $ dim checkpatch origin/drm-tip 96062a805ac2 drm/i915: fix whitelist selftests with readonly registers -:12: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrap

[Intel-gfx] [PATCH] drm/i915: fix whitelist selftests with readonly registers

From: Lionel Landwerlin When a register is readonly there is not much we can tell about its value (apart from its default value?). This can be covered by tests exercising the value of the register from userspace. For PS_INVOCATION_COUNT we've got the following piglit tests : KHR-GL45.pipeli

Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: CTS fixes (rev7)

Okay to land? -Lionel On 29/06/2019 06:33, Patchwork wrote: == Series Details == Series: drm/i915: CTS fixes (rev7) URL : https://patchwork.freedesktop.org/series/62437/ State : success == Summary == CI Bug Log - changes from CI_DRM_6380_full -> Patchwork_13469_full ===

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v3,1/2] drm/i915: Add support for retrying hotplug

== Series Details == Series: series starting with [v3,1/2] drm/i915: Add support for retrying hotplug URL : https://patchwork.freedesktop.org/series/62965/ State : success == Summary == CI Bug Log - changes from CI_DRM_6384_full -> Patchwork_13471_full =

[Intel-gfx] [PATCH 5/9] docs: fix some broken references due to txt->rst renames

There are three left-overs from the recent file renames, probably due to some other conflicting patch. Fix them. Signed-off-by: Mauro Carvalho Chehab Acked-by: Wolfram Sang Acked-by: Daniel Vetter --- Documentation/devicetree/bindings/arm/idle-states.txt | 2 +- drivers/gpu/drm/i915/intel_run

[Intel-gfx] [PATCH 0/9] Some doc fixes

This patch series is against linux-next (next-20190627). I doubt those would apply cleanly against docs next tree. So, please apply it via the subsystem trees. Otherwise, they could be pushed by the end of the merge window or for -rc1 via a docs tree. Most, if not all were I already sent. Mauro

[Intel-gfx] XDC 2019: 10 days left to submit your talks!

Hello! Onlyh 10 days to go to submit your talks, workshops or demos for this year's X.Org Developer Conference, which will be taking place in beautiful Montréal, Canada on October 2-4, 2019! Whether it's the Linux kernel, Mesa, DRM, Wayland or X11, if it's related to the Open Source graphics stac

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/guc: Avoid reclaim locks during reset

== Series Details == Series: series starting with [1/2] drm/i915/guc: Avoid reclaim locks during reset URL : https://patchwork.freedesktop.org/series/62973/ State : success == Summary == CI Bug Log - changes from CI_DRM_6385 -> Patchwork_13473 =

[Intel-gfx] [PATCH 2/2] drm/i915: Markup potential lock for i915_active

Make the lockchains more deterministic via i915_active by flagging the potential lock. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_active.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c index cb6a1eadf

[Intel-gfx] [PATCH 1/2] drm/i915/guc: Avoid reclaim locks during reset

During reset, we must be very selective in which locks we take as most are tainted by being held across a wait or reclaim (kmalloc) which implicitly waits. Inside the guc reset path, we reset the ADS to sane defaults, but must keep it pinned from initialisation to avoid having to pin it during rese

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix TypeC port mode switching (rev8)

== Series Details == Series: drm/i915: Fix TypeC port mode switching (rev8) URL : https://patchwork.freedesktop.org/series/61590/ State : success == Summary == CI Bug Log - changes from CI_DRM_6381_full -> Patchwork_13470_full Summary -