Re: [Intel-gfx] [PATCH 13/17] drm/i915: Introduce better global state handling

2020-01-27 Thread Imre Deak
On Mon, Jan 20, 2020 at 07:47:24PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Our current global state handling is pretty ad-hoc. Let's try to > make it better by imitating the standard drm core private object > approach. > > The reason why we don't want to directly use the private ob

Re: [Intel-gfx] [PATCH 13/17] drm/i915: Introduce better global state handling

2020-01-22 Thread Ville Syrjälä
On Wed, Jan 22, 2020 at 07:00:27PM +, Souza, Jose wrote: > On Mon, 2020-01-20 at 19:47 +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Our current global state handling is pretty ad-hoc. Let's try to > > make it better by imitating the standard drm core private object > > approach

Re: [Intel-gfx] [PATCH 13/17] drm/i915: Introduce better global state handling

2020-01-22 Thread Souza, Jose
On Mon, 2020-01-20 at 19:47 +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Our current global state handling is pretty ad-hoc. Let's try to > make it better by imitating the standard drm core private object > approach. > > The reason why we don't want to directly use the private objects >

[Intel-gfx] [PATCH 13/17] drm/i915: Introduce better global state handling

2020-01-20 Thread Ville Syrjala
From: Ville Syrjälä Our current global state handling is pretty ad-hoc. Let's try to make it better by imitating the standard drm core private object approach. The reason why we don't want to directly use the private objects is locking; Each private object has its own lock so if we introduce any