search for: bo_vm

...gt; I strongly believe you guys stumbled over one of the core problems with the VM here and I think that reference counting is the right answer to solving this. > > The big question is that what is reference counted and in which direction does the dependency points, e.g. we have here VM, BO, BO_VM and Mapping objects. > > Those patches here suggest a counted Mapping -> VM reference and I'm pretty sure that this isn't a good idea. What we should rather really have is a BO -> VM or BO_VM ->VM reference. In other words that each BO which is part of the VM keeps a referen...

...led over one of the core problems >> with the VM here and I think that reference counting is the right >> answer to solving this. >> >> The big question is that what is reference counted and in which >> direction does the dependency points, e.g. we have here VM, BO, BO_VM >> and Mapping objects. >> >> Those patches here suggest a counted Mapping -> VM reference and I'm >> pretty sure that this isn't a good idea. What we should rather really >> have is a BO -> VM or BO_VM ->VM reference. In other words that each >...

...>>> with the VM here and I think that reference counting is the right >>> answer to solving this. >>> >>> The big question is that what is reference counted and in which >>> direction does the dependency points, e.g. we have here VM, BO, >>> BO_VM and Mapping objects. >>> >>> Those patches here suggest a counted Mapping -> VM reference and I'm >>> pretty sure that this isn't a good idea. What we should rather >>> really have is a BO -> VM or BO_VM ->VM reference. In other words >>...

...very driver implement a driver >>>>> specific way of keeping this connection? >>>> >>>> Flexibility. For example on amdgpu the mappings of a BO are groups >>>> by VM address spaces. >>>> >>>> E.g. the BO points to multiple bo_vm structures which in turn have >>>> lists of their mappings. >>> >>> Isn't this (almost) the same relationship I introduce with the GPUVA >>> manager? >>> >>> If you would switch over to the GPUVA manager right now, it would be >>...

...>>>>>> driver specific way of keeping this connection? >>>>> >>>>> Flexibility. For example on amdgpu the mappings of a BO are groups >>>>> by VM address spaces. >>>>> >>>>> E.g. the BO points to multiple bo_vm structures which in turn have >>>>> lists of their mappings. >>>> >>>> Isn't this (almost) the same relationship I introduce with the >>>> GPUVA manager? >>>> >>>> If you would switch over to the GPUVA manager right no...

...;> driver specific way of keeping this connection? >>>>>> >>>>>> Flexibility. For example on amdgpu the mappings of a BO are groups >>>>>> by VM address spaces. >>>>>> >>>>>> E.g. the BO points to multiple bo_vm structures which in turn have >>>>>> lists of their mappings. >>>>> >>>>> Isn't this (almost) the same relationship I introduce with the >>>>> GPUVA manager? >>>>> >>>>> If you would switch over to th...