On ke, 2016-08-17 at 09:57 +0100, Chris Wilson wrote:
> On Wed, Aug 17, 2016 at 11:47:07AM +0300, Joonas Lahtinen wrote:
> >
> > On ti, 2016-08-16 at 11:42 +0100, Chris Wilson wrote:
> > >
> > > @@ -278,6 +283,9 @@ static void eb_destroy(struct eb_vmas *eb)
> > >
> > > static inline int use_cp
On Wed, Aug 17, 2016 at 11:47:07AM +0300, Joonas Lahtinen wrote:
> On ti, 2016-08-16 at 11:42 +0100, Chris Wilson wrote:
> > @@ -278,6 +283,9 @@ static void eb_destroy(struct eb_vmas *eb)
> >
> > static inline int use_cpu_reloc(struct drm_i915_gem_object *obj)
> > {
> > + if (DBG_USE_CPU_RELO
On ti, 2016-08-16 at 11:42 +0100, Chris Wilson wrote:
> @@ -278,6 +283,9 @@ static void eb_destroy(struct eb_vmas *eb)
>
> static inline int use_cpu_reloc(struct drm_i915_gem_object *obj)
> {
> + if (DBG_USE_CPU_RELOC)
> + return DBG_USE_CPU_RELOC > 0;
If DBG_USE_CPU_RELOC == 0
With the introduction of the reloc page cache, we are just one step away
from refactoring the relocation write functions into one. Not only does
it tidy the code (slightly), but it greatly simplifies the control logic
much to gcc's satisfaction.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i9
