search for: virtio_xmb

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

Did you mean: virtio_mb
2018 May 03
2
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") They should have already guaranteed that virtio_Xmb() will be OK for hardware devices when vq->weak_barriers is false. If my understanding is correct, the barriers used in this case are overkill. So Michael's patch is to make the barriers weaker (or better). Best regards, Tiwei Bie
2018 May 03
2
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...patch of > > "[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg" > > ? > > Thanks We already have below commit and some other related commits in the tree: 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") They should have already guaranteed that virtio_Xmb() will be OK for hardware devices when vq->weak_barriers is false. If my understanding is correct, the barriers used in this case are overkill. So Michael's patch is to make the barriers weaker (or better). Best regards, Tiwei Bie
2018 May 03
1
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...> > > > ? > > > > > > Thanks > > We already have below commit and some other related commits > > in the tree: > > > > 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") > > > > They should have already guaranteed that virtio_Xmb() will > > be OK for hardware devices when vq->weak_barriers is false. > > If my understanding is correct, the barriers used in this > > case are overkill. So Michael's patch is to make the barriers > > weaker (or better). > > > > Best regards, > >...
2018 May 03
0
[RFC] virtio: support VIRTIO_F_IO_BARRIER
...ring: switch to dma_XX barriers for rpmsg" >> >> ? >> >> Thanks > We already have below commit and some other related commits > in the tree: > > 7b21e34fd1c2 ("virtio: harsher barriers for rpmsg.") > > They should have already guaranteed that virtio_Xmb() will > be OK for hardware devices when vq->weak_barriers is false. > If my understanding is correct, the barriers used in this > case are overkill. So Michael's patch is to make the barriers > weaker (or better). > > Best regards, > Tiwei Bie Well, I think we need dma...
2018 May 03
6
[RFC] virtio: support VIRTIO_F_IO_BARRIER
This patch introduces the support for VIRTIO_F_IO_BARRIER. When this feature is negotiated, driver will use the barriers suitable for hardware devices. Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> --- drivers/virtio/virtio_ring.c | 5 +++++ include/uapi/linux/virtio_config.h | 8 +++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ring.c
2018 May 03
6
[RFC] virtio: support VIRTIO_F_IO_BARRIER
This patch introduces the support for VIRTIO_F_IO_BARRIER. When this feature is negotiated, driver will use the barriers suitable for hardware devices. Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> --- drivers/virtio/virtio_ring.c | 5 +++++ include/uapi/linux/virtio_config.h | 8 +++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_ring.c