On 12/04/2014 09:48 AM, Chris Wilson wrote:
On Wed, Dec 03, 2014 at 02:59:24PM +0000, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx>
Multiple GGTT VMAs per object will be introduced in the near future which will
make it impossible to guarantee normal GGTT view is at the head of the list.
Purpose of this patch is to break this assumption straight away so any
potential hidden assumptions in the code base can be bisected to this
simple patch.
No, please don't. The rationale for putting ggtt first is because it
puts the one vma that every object is likely to use at the front, and
makes it also the first in the list for debugging.
This came from talking with Daniel, but I don't understand why every
object is likely to have a GGTT mapping?
With multiple GGTT views it may happen that only single GGTT VMA exists
in the list but it is not the one current code would expect. So the idea
was to break that to flesh out any potential hidden assumptions in the
code. (I did not find any by just looking though.)
What kind of debugging you have in mind, error capture? Or actually
inspecting memory of a live kernel?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
