Searched refs:vmas (Results 1 – 5 of 5) sorted by relevance
21 struct xe_vma **vmas; member56 madvise_range->vmas = kmalloc_objs(*madvise_range->vmas, max_vmas); in get_vmas()57 if (!madvise_range->vmas) in get_vmas()72 __vmas = krealloc(madvise_range->vmas, in get_vmas()73 max_vmas * sizeof(*madvise_range->vmas), in get_vmas()76 kfree(madvise_range->vmas); in get_vmas()79 madvise_range->vmas = __vmas; in get_vmas()82 madvise_range->vmas[madvise_range->num_vmas] = vma; in get_vmas()87 kfree(madvise_range->vmas); in get_vmas()95 struct xe_vma **vmas, int num_vmas, in madvise_preferred_mem_loc() argument[all …]
198 self.vmas = []205 self.vmas.append(VMA(223 self.vmas[-1].stats[param] = {'type': None, 'value': value}226 yield from self.vmas
36 operations never involve heavyweight structures like vmas (in fact the40 Terabytes. Too many vmas would be needed for that.
122 invalidated vmas (due to eviction and userptr invalidation) etc.
234 only a subset of vmas are selected for rebind. In this case, all vmas that are