Re: [Intel-gfx] [PATCH 1/2] drm/i915: Split intel_engine allocation and initialisation

2017-01-23 Thread Joonas Lahtinen
On ma, 2017-01-23 at 09:57 +, Chris Wilson wrote: > On Mon, Jan 23, 2017 at 11:41:12AM +0200, Joonas Lahtinen wrote: > > > > On la, 2017-01-21 at 14:50 +, Chris Wilson wrote: > > > > > > In order to reset the GPU early on in the module load sequence, we need > > > to allocate the basic

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Split intel_engine allocation and initialisation

2017-01-23 Thread Chris Wilson
On Mon, Jan 23, 2017 at 11:41:12AM +0200, Joonas Lahtinen wrote: > On la, 2017-01-21 at 14:50 +, Chris Wilson wrote: > > In order to reset the GPU early on in the module load sequence, we need > > to allocate the basic engine structs (to populate the mmio offsets etc). > > Currently, the

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Split intel_engine allocation and initialisation

2017-01-23 Thread Joonas Lahtinen
On la, 2017-01-21 at 14:50 +, Chris Wilson wrote: > In order to reset the GPU early on in the module load sequence, we need > to allocate the basic engine structs (to populate the mmio offsets etc). > Currently, the engine initialisation allocates both the base struct and > also allocate

[Intel-gfx] [PATCH 1/2] drm/i915: Split intel_engine allocation and initialisation

2017-01-21 Thread Chris Wilson
In order to reset the GPU early on in the module load sequence, we need to allocate the basic engine structs (to populate the mmio offsets etc). Currently, the engine initialisation allocates both the base struct and also allocate auxiliary objects, which depend upon state setup quite late in the