Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-17 Thread Tvrtko Ursulin
, Terrence Subject: Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly Hi, On 13/03/2017 09:37, Zhenyu Wang wrote: On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: On 10/03/2017 10:09, Chris Wilson wrote: On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-17 Thread Xu, Terrence
>Subject: Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU >more thouroughly > > >Hi, > >On 13/03/2017 09:37, Zhenyu Wang wrote: >> On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: >>> >>> On 10/03/2017 10:09, Chris Wilson wrote: >>&g

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-17 Thread Tvrtko Ursulin
Hi, On 13/03/2017 09:37, Zhenyu Wang wrote: On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: On 10/03/2017 10:09, Chris Wilson wrote: On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin If we avoid initializing forcewake domains when running as a guest,

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-13 Thread Chris Wilson
On Mon, Mar 13, 2017 at 09:47:15AM +, Tvrtko Ursulin wrote: > > On 13/03/2017 09:37, Zhenyu Wang wrote: > >On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: > >> > >>On 10/03/2017 10:09, Chris Wilson wrote: > >>>On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: > From: Tvrt

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-13 Thread Tvrtko Ursulin
On 13/03/2017 09:37, Zhenyu Wang wrote: On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: On 10/03/2017 10:09, Chris Wilson wrote: On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin If we avoid initializing forcewake domains when running as a guest, and

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-13 Thread Zhenyu Wang
On 2017.03.13 09:26:26 +, Tvrtko Ursulin wrote: > > On 10/03/2017 10:09, Chris Wilson wrote: > > On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: > > > From: Tvrtko Ursulin > > > > > > If we avoid initializing forcewake domains when running as > > > a guest, and also use gen2

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-13 Thread Tvrtko Ursulin
On 10/03/2017 10:09, Chris Wilson wrote: On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin If we avoid initializing forcewake domains when running as a guest, and also use gen2 mmio accessors in that case, we can avoid the timer traffic and any looping throu

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-10 Thread Mika Kuoppala
Chris Wilson writes: > On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: >> From: Tvrtko Ursulin >> >> If we avoid initializing forcewake domains when running as >> a guest, and also use gen2 mmio accessors in that case, we >> can avoid the timer traffic and any looping through th

Re: [Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-10 Thread Chris Wilson
On Fri, Mar 10, 2017 at 09:57:47AM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > If we avoid initializing forcewake domains when running as > a guest, and also use gen2 mmio accessors in that case, we > can avoid the timer traffic and any looping through the > forcewake code which is cu

[Intel-gfx] [PATCH] drm/i915/vgpu: Neuter forcewakes for VGPU more thouroughly

2017-03-10 Thread Tvrtko Ursulin
From: Tvrtko Ursulin If we avoid initializing forcewake domains when running as a guest, and also use gen2 mmio accessors in that case, we can avoid the timer traffic and any looping through the forcewake code which is currently just so it can end up in the no-op forcewake implementation. Signed