On Wed, 29 Apr 2015, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > On Wed, Apr 29, 2015 at 09:49:30AM +0300, Mika Kuoppala wrote: >> When we have bound vma into an address space, the layout >> of page table structures is immutable. So we can be absolutely >> certain that if vma is already bound, there is no need to >> (re)allocate a virtual address range for it. >> >> v2: - add sanity checks and remove superfluous GLOBAL_BIND set >> - we might do update for an unbound vma (Chris) >> >> v3: s/u32/unsigned (Chris) > > Go back to v2. Sorry, seems like u32 is being used throughout this > callchain and so needs to be fixed all together. v2 pushed to drm-intel-next-queued, with Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90224 Thanks for the patch and review. BR, Jani. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
