search for: vm_destroy

...ch >>> VM_BO, as we do already. Now instead of simply increasing the >>> reference count for each >>> mapping as well, we'd need a *mandatory* driver callback that is >>> called when the GPUVM >>> reference count drops to zero. Maybe something like vm_destroy(). >>> >>> The reason is that GPUVM can't just remove all mappings from the >>> tree nor can it free them >>> by itself, since drivers might use them for tracking their allocated >>> page tables and/or >>> other stuff. >>> >&gt...

...gt; reference for each >> VM_BO, as we do already. Now instead of simply increasing the >> reference count for each >> mapping as well, we'd need a *mandatory* driver callback that is >> called when the GPUVM >> reference count drops to zero. Maybe something like vm_destroy(). >> >> The reason is that GPUVM can't just remove all mappings from the tree >> nor can it free them >> by itself, since drivers might use them for tracking their allocated >> page tables and/or >> other stuff. >> >> Now, let's think about...

...VM_BO, as we do already. Now instead of simply increasing the >>>> reference count for each >>>> mapping as well, we'd need a *mandatory* driver callback that is >>>> called when the GPUVM >>>> reference count drops to zero. Maybe something like vm_destroy(). >>>> >>>> The reason is that GPUVM can't just remove all mappings from the >>>> tree nor can it free them >>>> by itself, since drivers might use them for tracking their >>>> allocated page tables and/or >>>> other stu...

...GPUVM and take a > reference for each > VM_BO, as we do already. Now instead of simply increasing the > reference count for each > mapping as well, we'd need a *mandatory* driver callback that is > called when the GPUVM > reference count drops to zero. Maybe something like vm_destroy(). > > The reason is that GPUVM can't just remove all mappings from the tree > nor can it free them > by itself, since drivers might use them for tracking their allocated > page tables and/or > other stuff. > > Now, let's think about the scope this callback might b...

...d still need to reference count a GPUVM and take a reference for each VM_BO, as we do already. Now instead of simply increasing the reference count for each mapping as well, we'd need a *mandatory* driver callback that is called when the GPUVM reference count drops to zero. Maybe something like vm_destroy(). The reason is that GPUVM can't just remove all mappings from the tree nor can it free them by itself, since drivers might use them for tracking their allocated page tables and/or other stuff. Now, let's think about the scope this callback might be called from. When a VM_BO is destroyed...

Hi, Virsh destroy is always failing with below error. [host:~]$ virsh destroy XYZ--2 error: Failed to destroy domain XYZ--2 error: Requested operation is not valid: domain is not running [host:~]$ virsh list --all Id Name State ---------------------------------------------------- - XYZ--2 shut off [host:~]$ host:~]$ libvirtd --version