Re: [PATCH 2/2] drm/i915: Unbind all vmas whose new cache_level doesn't agree with the neighbours

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 12, 2014 at 07:32:27PM +0200, ville.syrjala@xxxxxxxxxxxxxxx wrote:
> From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx>
> 
> When we change the cache_level for an object we need to make sure
> we don't put differing types of snoopable memory too close to each
> other on non-LLC machines.
> 
> Currently i915_gem_object_set_cache_level() will stop looking when
> it finds just one vma that has such a conflict. Drop the bogus break
> statement to make sure it will unbind all vmas which need to be moved
> around to avoid the conflict.
> 
> I suppose this is a theoretical issue as currently we don't enable
> ppgtt on non-LLC machines, so each object can only have one vma.
> 
> Signed-off-by: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx>

Both patches merged, thanks.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx





[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux