search for: l313

Displaying 6 results from an estimated 6 matches for "l313".

Did you mean: 313
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
On 2019/10/24 ??4:03, Jason Wang wrote: > > On 2019/10/24 ??12:21, Tiwei Bie wrote: >> On Wed, Oct 23, 2019 at 06:29:21PM +0800, Jason Wang wrote: >>> On 2019/10/23 ??6:11, Tiwei Bie wrote: >>>> On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote: >>>>> On 2019/10/23 ??3:07, Tiwei Bie wrote: >>>>>> On Wed, Oct 23, 2019 at
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
On 2019/10/24 ??4:03, Jason Wang wrote: > > On 2019/10/24 ??12:21, Tiwei Bie wrote: >> On Wed, Oct 23, 2019 at 06:29:21PM +0800, Jason Wang wrote: >>> On 2019/10/23 ??6:11, Tiwei Bie wrote: >>>> On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote: >>>>> On 2019/10/23 ??3:07, Tiwei Bie wrote: >>>>>> On Wed, Oct 23, 2019 at
2024 Feb 16
1
[PATCH] nouveau: offload fence uevents work to workqueue
...ould also make stuff like reliably stopping the right amount of schedulers in tdr much more robust. -Sima > > - Danilo > > > > > Cheers, Sima > > > > > > > > [1] https://elixir.bootlin.com/linux/v6.8-rc3/source/drivers/gpu/drm/nouveau/nouveau_drm.c#L313 > > > > > > > > > > > I'm not sure we should care differently, but I guess it'd be good to > > > > annotate it all in case the wq subsystem's idea of how much such deadlocks > > > > are real changes. > > > > > &g...
2019 Oct 24
0
[PATCH v2] vhost: introduce mdev based hardware backend
.... We already have VHOST_SET_OWNER in vhost now, parent can handle the commands in its .kick_vq() which is called by vq's .handle_kick callback. Virtio-user did something similar: https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322 > > > > But is there any chance to use DMA address? I'm asking since the API > > then tends to be device specific. > > > I wonder whether we can introduce MAP IOMMU notifier and get DMA mappings > from that. I think this will complicate things unnecessar...
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
...VHOST_SET_OWNER in vhost now, parent can handle > the commands in its .kick_vq() which is called by vq's .handle_kick > callback. Virtio-user did something similar: > > https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322 This probably means a process context is required, something like kthread that is used by vhost which seems a burden for parent. Or we can extend ioctl to processing kick in the system call context. > >> >>> But is there any chance to use DMA address? I'm asking sin...
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
...VHOST_SET_OWNER in vhost now, parent can handle > the commands in its .kick_vq() which is called by vq's .handle_kick > callback. Virtio-user did something similar: > > https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322 This probably means a process context is required, something like kthread that is used by vhost which seems a burden for parent. Or we can extend ioctl to processing kick in the system call context. > >> >>> But is there any chance to use DMA address? I'm asking sin...