Re: [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+

2020-07-14 Thread kernel test robot
Hi Ville, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on drm-tip/drm-tip v5.8-rc5 next-20200714] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest

Re: [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+

2020-07-14 Thread Ville Syrjälä
On Tue, Jul 14, 2020 at 08:13:03PM +0100, Chris Wilson wrote: > Quoting Ville Syrjala (2020-07-14 19:51:28) > > From: Ville Syrjälä > > > > Since g4x the CFB base only takes a 28bit offset into stolen. > > Not sure if the CFB is allowed to start below that limit but > > then extend beyond it. Let

Re: [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+

2020-07-14 Thread Chris Wilson
Quoting Ville Syrjala (2020-07-14 19:51:28) > From: Ville Syrjälä > > Since g4x the CFB base only takes a 28bit offset into stolen. > Not sure if the CFB is allowed to start below that limit but > then extend beyond it. Let's assume not and just restrict the > allocation to the first 256MiB (in t

[Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+

2020-07-14 Thread Ville Syrjala
From: Ville Syrjälä Since g4x the CFB base only takes a 28bit offset into stolen. Not sure if the CFB is allowed to start below that limit but then extend beyond it. Let's assume not and just restrict the allocation to the first 256MiB (in the unlikely case we have more stolen than that). Signed