Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-09 Thread Kasireddy, Vivek
Hi Ville, > On Wed, Feb 09, 2022 at 01:47:01AM +, Kasireddy, Vivek wrote: > > Hi Ville, > > > > > > > > On Tue, Feb 08, 2022 at 05:10:42AM +, Kasireddy, Vivek wrote: > > > > Hi Tvrtko, Ville, > > > > > > > > > On 07/02/2022 13:24, Ville Syrjälä wrote: > > > > > > On Mon, Feb 07, 2022 at 11

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-08 Thread Ville Syrjälä
On Wed, Feb 09, 2022 at 01:47:01AM +, Kasireddy, Vivek wrote: > Hi Ville, > > > > > On Tue, Feb 08, 2022 at 05:10:42AM +, Kasireddy, Vivek wrote: > > > Hi Tvrtko, Ville, > > > > > > > On 07/02/2022 13:24, Ville Syrjälä wrote: > > > > > On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursu

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-08 Thread Kasireddy, Vivek
Hi Ville, > > On Tue, Feb 08, 2022 at 05:10:42AM +, Kasireddy, Vivek wrote: > > Hi Tvrtko, Ville, > > > > > On 07/02/2022 13:24, Ville Syrjälä wrote: > > > > On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursulin wrote: > > > >> > > > >> On 07/02/2022 10:58, Ville Syrjälä wrote: > > > >>> O

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Ville Syrjälä
On Tue, Feb 08, 2022 at 05:10:42AM +, Kasireddy, Vivek wrote: > Hi Tvrtko, Ville, > > > On 07/02/2022 13:24, Ville Syrjälä wrote: > > > On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursulin wrote: > > >> > > >> On 07/02/2022 10:58, Ville Syrjälä wrote: > > >>> On Thu, Feb 03, 2022 at 05:22:

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Kasireddy, Vivek
Hi Tvrtko, Ville, > On 07/02/2022 13:24, Ville Syrjälä wrote: > > On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursulin wrote: > >> > >> On 07/02/2022 10:58, Ville Syrjälä wrote: > >>> On Thu, Feb 03, 2022 at 05:22:10PM -0800, Vivek Kasireddy wrote: > On platforms capable of allowing 8K (7

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Tvrtko Ursulin
On 07/02/2022 13:24, Ville Syrjälä wrote: On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursulin wrote: On 07/02/2022 10:58, Ville Syrjälä wrote: On Thu, Feb 03, 2022 at 05:22:10PM -0800, Vivek Kasireddy wrote: On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more fra

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Ville Syrjälä
On Mon, Feb 07, 2022 at 11:47:16AM +, Tvrtko Ursulin wrote: > > On 07/02/2022 10:58, Ville Syrjälä wrote: > > On Thu, Feb 03, 2022 at 05:22:10PM -0800, Vivek Kasireddy wrote: > >> On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or > >> more framebuffers/scanout buffers resul

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Tvrtko Ursulin
On 07/02/2022 10:58, Ville Syrjälä wrote: On Thu, Feb 03, 2022 at 05:22:10PM -0800, Vivek Kasireddy wrote: On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more framebuffers/scanout buffers results in only one that is mappable/ fenceable. Therefore, pageflipping between th

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Ville Syrjälä
On Thu, Feb 03, 2022 at 05:22:10PM -0800, Vivek Kasireddy wrote: > On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or > more framebuffers/scanout buffers results in only one that is mappable/ > fenceable. Therefore, pageflipping between these 2 FBs where only one > is mappable/fe

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-07 Thread Tvrtko Ursulin
On 04/02/2022 01:22, Vivek Kasireddy wrote: On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more framebuffers/scanout buffers results in only one that is mappable/ fenceable. Therefore, pageflipping between these 2 FBs where only one is mappable/fenceable creates latencies

[Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-03 Thread Vivek Kasireddy
On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more framebuffers/scanout buffers results in only one that is mappable/ fenceable. Therefore, pageflipping between these 2 FBs where only one is mappable/fenceable creates latencies large enough to miss alternate vblanks thereby