Re: [Intel-gfx] [PATCH] drm/i915: After hibernation, discard the unbound list

2013-02-10 Thread Chris Wilson
On Sun, Feb 10, 2013 at 11:04:17AM -0800, Ben Widawsky wrote: > I'm confused by how you're going about this. To reorder what you said, > if an object is on the unbound list the GPU is done with it, and it may > require clflushing if on a non-LLC system. Right, the objects on the unbound list are e

Re: [Intel-gfx] [PATCH] drm/i915: After hibernation, discard the unbound list

2013-02-10 Thread Ben Widawsky
On Thu, Feb 07, 2013 at 10:27:47AM +, Chris Wilson wrote: > The unbound list is an optimisation to track objects that have been > evicted from the GTT but remain untouched by the CPU. After hibernation, > all memory is in the CPU domain (having been restored from a disk image) > and so we need

[Intel-gfx] [PATCH] drm/i915: After hibernation, discard the unbound list

2013-02-07 Thread Chris Wilson
The unbound list is an optimisation to track objects that have been evicted from the GTT but remain untouched by the CPU. After hibernation, all memory is in the CPU domain (having been restored from a disk image) and so we need to restore the domain tracking upon the objects. However, for the unbo

[Intel-gfx] [PATCH] drm/i915: After hibernation, discard the unbound list

2013-02-07 Thread Chris Wilson
The unbound list is an optimisation to track objects that have been evicted from the GTT but remain untouched by the CPU. After hibernation, all memory is in the CPU domain (having been restored from a disk image) and so we need to restore the domain tracking upon the objects. However, for the unbo