Displaying 6 results from an estimated 6 matches for "vdpasim_unbind_mm".
Did you mean:
vdpasim_bind_mm
2023 Mar 23
1
[PATCH v3 8/8] vdpa_sim: add support for user VA
...m = vdpa_to_sim(vdpa);
> + struct vdpasim_mm_work mm_work;
> +
> + mm_work.vdpasim = vdpasim;
> + mm_work.mm_to_bind = mm;
> +
> + vdpasim_worker_change_mm_sync(vdpasim, &mm_work);
> +
> + return mm_work.ret;
> +}
> +
> +static void vdpasim_unbind_mm(struct vdpa_device *vdpa)
> +{
> + struct vdpasim *vdpasim = vdpa_to_sim(vdpa);
> + struct vdpasim_mm_work mm_work;
> +
> + mm_work.vdpasim = vdpasim;
> + mm_work.mm_to_bind = NULL;
> +
> + vdpasim_worker_change_mm_sync(vdpasim, &mm_work);
&...
2023 Mar 14
1
[PATCH v2 8/8] vdpa_sim: add support for user VA
...struct vdpasim *vdpasim = vdpa_to_sim(vdpa);
> + int ret;
> +
> + mutex_lock(&vdpasim->mutex);
> + ret = vdpasim_worker_bind_mm(vdpasim, mm);
> + mutex_unlock(&vdpasim->mutex);
> +
> + return ret;
> +}
> +
> +static void vdpasim_unbind_mm(struct vdpa_device *vdpa)
> +{
> + struct vdpasim *vdpasim = vdpa_to_sim(vdpa);
> +
> + mutex_lock(&vdpasim->mutex);
> + vdpasim_worker_unbind_mm(vdpasim);
> + mutex_unlock(&vdpasim->mutex);
> +}
> +
> static int vdpasim_dma_map(stru...
2023 Mar 24
1
[PATCH v3 8/8] vdpa_sim: add support for user VA
...> + struct vdpasim *vdpasim = vdpa_to_sim(vdpa);
> + struct vdpasim_mm_work mm_work;
> +
> + mm_work.vdpasim = vdpasim;
> + mm_work.mm_to_bind = mm;
> +
> + vdpasim_worker_change_mm_sync(vdpasim, &mm_work);
> +
> + return mm_work.ret;
> +}
> +
> +static void vdpasim_unbind_mm(struct vdpa_device *vdpa)
> +{
> + struct vdpasim *vdpasim = vdpa_to_sim(vdpa);
> + struct vdpasim_mm_work mm_work;
> +
> + mm_work.vdpasim = vdpasim;
> + mm_work.mm_to_bind = NULL;
> +
> + vdpasim_worker_change_mm_sync(vdpasim, &mm_work);
> +}
> +
> static in...
2023 Mar 21
3
[PATCH v3 5/8] vdpa_sim: make devices agnostic for work management
Let's move work management inside the vdpa_sim core.
This way we can easily change how we manage the works, without
having to change the devices each time.
Acked-by: Eugenio P??rez Martin <eperezma at redhat.com>
Acked-by: Jason Wang <jasowang at redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
---
drivers/vdpa/vdpa_sim/vdpa_sim.h | 3 ++-
2023 Mar 02
8
[PATCH v2 0/8] vdpa_sim: add support for user VA
v2:
- rebased on Linus' tree, commit ae3419fbac84 ("vc_screen: don't clobber
return value in vcs_read")
- removed `struct task_struct *owner` param (unused for now, maybe
?useful to support cgroups) [Jason]
- add unbind_mm callback [Jason]
- call the new unbind_mm callback during the release [Jason]
- avoid to call bind_mm callback after the reset, since the device
?is not
2023 Apr 04
9
[PATCH v5 0/9] vdpa_sim: add support for user VA
This series adds support for the use of user virtual addresses in the
vDPA simulator devices.
The main reason for this change is to lift the pinning of all guest memory.
Especially with virtio devices implemented in software.
The next step would be to generalize the code in vdpa-sim to allow the
implementation of in-kernel software devices. Similar to vhost, but using vDPA
so we can reuse the