Re: [Intel-gfx] [PATCH] drm/i915: Add not fenceable reason to not enable FBC

2019-03-25 Thread Souza, Jose
On Fri, 2019-03-22 at 07:06 +, Chris Wilson wrote: > Quoting José Roberto de Souza (2019-03-22 00:42:59) > > There is some kms_frontbuffer_tracking failures due FBC being > > disabled with the reason "framebuffer not tiled or fenced". > > Although the test is setting up everything correctly to

Re: [Intel-gfx] [PATCH] drm/i915: Add not fenceable reason to not enable FBC

2019-03-22 Thread Chris Wilson
Quoting José Roberto de Souza (2019-03-22 00:42:59) > There is some kms_frontbuffer_tracking failures due FBC being > disabled with the reason "framebuffer not tiled or fenced". > Although the test is setting up everything correctly to have > FBC enabled sporadically it is failing, due the alignmen

Re: [Intel-gfx] [PATCH] drm/i915: Add not fenceable reason to not enable FBC

2019-03-21 Thread Souza, Jose
After sent I notice that the commit descriptions feels strange to read, maybe changing to "drm/i915: Add 'not fenceable' reason to not enable FBC" makes it better, any tips? On Thu, 2019-03-21 at 17:42 -0700, José Roberto de Souza wrote: > There is some kms_frontbuffer_tracking failures due FBC be

[Intel-gfx] [PATCH] drm/i915: Add not fenceable reason to not enable FBC

2019-03-21 Thread José Roberto de Souza
There is some kms_frontbuffer_tracking failures due FBC being disabled with the reason "framebuffer not tiled or fenced". Although the test is setting up everything correctly to have FBC enabled sporadically it is failing, due the alignment and size restrictions in __i915_vma_set_map_and_fenceable(