Re: [Intel-gfx] Enabling i915.fastboot=1 by default

Hi, On 06-06-18 12:43, Maarten Lankhorst wrote: Op 06-06-18 om 11:54 schreef Hans de Goede: Hi, On 06-06-18 11:36, Maarten Lankhorst wrote: Op 06-06-18 om 11:09 schreef Hans de Goede: Hi All, So I'm working on making Linux boot in a complete flickerfree manner (no modesets, no black screens

[Intel-gfx] [drm-intel:topic/core-for-CI 7/8] undefined reference to `save_stack_trace'

tree: git://anongit.freedesktop.org/drm-intel topic/core-for-CI head: e2ea2db1734a0e38b89e4d706b5f9ad9f73b1543 commit: 72041f9847abb05b9d4d7dea17631b579191ca99 [7/8] RFC: debugobjects: capture stack traces at _init() time config: alpha-allyesconfig (attached as .config) compiler: alpha-linux-g

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Export number of fail injection checkpoints through debugfs

== Series Details == Series: drm/i915: Export number of fail injection checkpoints through debugfs URL : https://patchwork.freedesktop.org/series/44347/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4282 -> Patchwork_9214 = == Summary - WARNING == Minor unknown changes c

Re: [Intel-gfx] [PATCH] drm/i915: Export number of fail injection checkpoints through debugfs

Quoting Michał Winiarski (2018-06-06 12:33:56) > We'd like to start testing module load with fault injection. To avoid > making any asumptions on number of available fault injection > checkpoints (either in IGT or in i915), we can compute it at runtime and > export it in debugfs. The idea was that

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Export number of fail injection checkpoints through debugfs

== Series Details == Series: drm/i915: Export number of fail injection checkpoints through debugfs URL : https://patchwork.freedesktop.org/series/44347/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Export number of fail injection checkpoints through debugfs -driv

[Intel-gfx] [PATCH] drm/i915: Export number of fail injection checkpoints through debugfs

We'd like to start testing module load with fault injection. To avoid making any asumptions on number of available fault injection checkpoints (either in IGT or in i915), we can compute it at runtime and export it in debugfs. Signed-off-by: Michał Winiarski Cc: Chris Wilson Cc: Imre Deak Cc: Jo

Re: [Intel-gfx] [PATCH v3 2/7] drm/i915/dp: Use intel_dp_aux_wait_done() to wait for previous aux xfer

On Thursday, May 17, 2018 3:21:13 PM PDT José Roberto de Souza wrote: > This reduces the spaghetti that intel_dp_aux_xfer() and reuses code. > The only difference is that now it will wait up to 10ms instead of > 3ms. > > Cc: Dhinakaran Pandiyan > Cc: Rodrigo Vivi > Signed-off-by: José Roberto de

Re: [Intel-gfx] [PATCH i-g-t v2 2/2] intel_gpu_overlay: Update for class:instance engine tracepoints

On 06/06/2018 11:29, Lionel Landwerlin wrote: On 06/06/18 10:02, Tvrtko Ursulin wrote: From: Tvrtko Ursulin A miminal hack to parse the new tracepoint format and invent new "ring id's" based on engine class and instance. v2:   * Make it a bit more future proof. (Lionel, Chris)   * Some assor

Re: [Intel-gfx] Enabling i915.fastboot=1 by default

Op 06-06-18 om 11:54 schreef Hans de Goede: > Hi, > > On 06-06-18 11:36, Maarten Lankhorst wrote: >> Op 06-06-18 om 11:09 schreef Hans de Goede: >>> Hi All, >>> >>> So I'm working on making Linux boot in a complete >>> flickerfree manner (no modesets, no black screens). >>> >>> I have this working

Re: [Intel-gfx] [PATCH i-g-t v2 2/2] intel_gpu_overlay: Update for class:instance engine tracepoints

On 06/06/18 10:02, Tvrtko Ursulin wrote: From: Tvrtko Ursulin A miminal hack to parse the new tracepoint format and invent new "ring id's" based on engine class and instance. v2: * Make it a bit more future proof. (Lionel, Chris) * Some assorted fixups to show forgotten engines. Signed-of

Re: [Intel-gfx] Enabling i915.fastboot=1 by default

Hi, On 06-06-18 11:36, Maarten Lankhorst wrote: Op 06-06-18 om 11:09 schreef Hans de Goede: Hi All, So I'm working on making Linux boot in a complete flickerfree manner (no modesets, no black screens). I have this working on various machines with Intel gfx, but I need to pass i915.fastboot=1

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3)

== Series Details == Series: series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3) URL : https://patchwork.freedesktop.org/series/44328/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4282_full -> Patchwork_9213_full

Re: [Intel-gfx] Enabling i915.fastboot=1 by default

Op 06-06-18 om 11:09 schreef Hans de Goede: > Hi All, > > So I'm working on making Linux boot in a complete > flickerfree manner (no modesets, no black screens). > > I have this working on various machines with Intel > gfx, but I need to pass i915.fastboot=1 on the kernel > commandline. > > I know

[Intel-gfx] Enabling i915.fastboot=1 by default

Hi All, So I'm working on making Linux boot in a complete flickerfree manner (no modesets, no black screens). I have this working on various machines with Intel gfx, but I need to pass i915.fastboot=1 on the kernel commandline. I know there was some talk about enabling this by default a while a

[Intel-gfx] [PATCH i-g-t v2 2/2] intel_gpu_overlay: Update for class:instance engine tracepoints

From: Tvrtko Ursulin A miminal hack to parse the new tracepoint format and invent new "ring id's" based on engine class and instance. v2: * Make it a bit more future proof. (Lionel, Chris) * Some assorted fixups to show forgotten engines. Signed-off-by: Tvrtko Ursulin Cc: Lionel Landwerlin

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Add WaKBLVECSSemaphoreWaitPoll

Quoting Mika Kuoppala (2018-06-06 09:40:11) > Chris Wilson writes: > > > Quoting Mika Kuoppala (2018-06-05 17:03:57) > >> There is a problem with kbl up to rev E0 where a heavy > >> memory/fabric traffic from adjacent engine(s) can cause an engine > >> reset to fail. This traffic can be from norm

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Add WaKBLVECSSemaphoreWaitPoll

Chris Wilson writes: > Quoting Mika Kuoppala (2018-06-05 17:03:57) >> There is a problem with kbl up to rev E0 where a heavy >> memory/fabric traffic from adjacent engine(s) can cause an engine >> reset to fail. This traffic can be from normal memory accesses >> or it can be from heavy polling on

Re: [Intel-gfx] [RFC] i915: make the probe asynchronous

On Wed, 06 Jun 2018, Feng Tang wrote: > Hi Jani, > > On Tue, Jun 05, 2018 at 11:18:46AM +0300, Jani Nikula wrote: >> On Tue, 05 Jun 2018, Feng Tang wrote: >> > Hi Jani, >> > >> > On Tue, Jun 05, 2018 at 10:41:04AM +0300, Jani Nikula wrote: >> >> On Mon, 04 Jun 2018, Feng Tang wrote: >> >> > i915

Re: [Intel-gfx] [PULL] gvt-fixes for 4.17

On 2018.04.19 15:39:48 +0800, Zhenyu Wang wrote: > > Hi, > > Here's current gvt fixes for 4.17 with several kernel warning > and other misc fixes as detailed below. > > p.s: I'll be on vacation from next week till May 2, Zhi will cover for me. > > Thanks > -- Looks this one got missed for merg

Re: [Intel-gfx] [PULL] drm-misc-next

Op 06-06-18 om 05:37 schreef Dave Airlie: > On 26 April 2018 at 20:53, Maarten Lankhorst > wrote: >> Hi Dave, >> >> This is my first pull request for v4.18. Only UAPI change is adding a >> generic plane >> alpha property, which replaces the driver specific ones in sun4i, rcar-du >> and atmel-hc

Re: [Intel-gfx] [RFC] i915: make the probe asynchronous

Hi Jani, On Tue, Jun 05, 2018 at 11:18:46AM +0300, Jani Nikula wrote: > On Tue, 05 Jun 2018, Feng Tang wrote: > > Hi Jani, > > > > On Tue, Jun 05, 2018 at 10:41:04AM +0300, Jani Nikula wrote: > >> On Mon, 04 Jun 2018, Feng Tang wrote: > >> > i915 driver's probe is one of the longest of pci devic

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3)

== Series Details == Series: series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3) URL : https://patchwork.freedesktop.org/series/44328/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4282 -> Patchwork_9213 = == Sum

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3)

== Series Details == Series: series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3) URL : https://patchwork.freedesktop.org/series/44328/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915/gtt: Invalidate GGTT c

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3)

== Series Details == Series: series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories (rev3) URL : https://patchwork.freedesktop.org/series/44328/ State : warning == Summary == $ dim checkpatch origin/drm-tip b4c3a32216a8 drm/i915/gtt: Invalida

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories

== Series Details == Series: series starting with [01/17] drm/i915/gtt: Invalidate GGTT caches after writing the gen6 page directories URL : https://patchwork.freedesktop.org/series/44328/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4282 -> Patchwork_9212 = == Summary -

<    1   2