Re: [Intel-gfx] [PATCH v4 5/8] drm/i915: Bump gen4+ fb stride limit to 256KiB

2019-01-30 Thread Ville Syrjälä
On Wed, Jan 30, 2019 at 10:01:04AM +, Chris Wilson wrote: > Quoting Daniel Vetter (2019-01-30 09:58:56) > > On Thu, Jan 24, 2019 at 08:59:36PM +0200, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > With gtt remapping plugged in we can simply raise the stride > > > limit on gen4+. L

Re: [Intel-gfx] [PATCH v4 5/8] drm/i915: Bump gen4+ fb stride limit to 256KiB

2019-01-30 Thread Chris Wilson
Quoting Daniel Vetter (2019-01-30 09:58:56) > On Thu, Jan 24, 2019 at 08:59:36PM +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > With gtt remapping plugged in we can simply raise the stride > > limit on gen4+. Let's just pick the limit to match the render > > engine max stride (256KiB

Re: [Intel-gfx] [PATCH v4 5/8] drm/i915: Bump gen4+ fb stride limit to 256KiB

2019-01-30 Thread Daniel Vetter
On Thu, Jan 24, 2019 at 08:59:36PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > With gtt remapping plugged in we can simply raise the stride > limit on gen4+. Let's just pick the limit to match the render > engine max stride (256KiB). > > No remapping CCS because the virtual address of

[Intel-gfx] [PATCH v4 5/8] drm/i915: Bump gen4+ fb stride limit to 256KiB

2019-01-24 Thread Ville Syrjala
From: Ville Syrjälä With gtt remapping plugged in we can simply raise the stride limit on gen4+. Let's just pick the limit to match the render engine max stride (256KiB). No remapping CCS because the virtual address of each page actually matters due to the new hash mode (WaCompressedResourceDisp