Displaying 3 results from an estimated 3 matches for "keystone_rproc_kick".
2018 Apr 19
4
[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg
On Thu, Apr 19, 2018 at 07:39:21PM +0200, Paolo Bonzini wrote:
> On 19/04/2018 19:35, Michael S. Tsirkin wrote:
> > virtio is using barriers to order memory accesses, thus
> > dma_wmb/rmb is a good match.
> >
> > Build-tested on x86: Before
> >
> > [mst at tuck linux]$ size drivers/virtio/virtio_ring.o
> > text data bss dec hex
2018 Apr 19
4
[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg
On Thu, Apr 19, 2018 at 07:39:21PM +0200, Paolo Bonzini wrote:
> On 19/04/2018 19:35, Michael S. Tsirkin wrote:
> > virtio is using barriers to order memory accesses, thus
> > dma_wmb/rmb is a good match.
> >
> > Build-tested on x86: Before
> >
> > [mst at tuck linux]$ size drivers/virtio/virtio_ring.o
> > text data bss dec hex
2018 Apr 19
0
[PATCH] virtio_ring: switch to dma_XX barriers for rpmsg
..._notify
>> (drivers/virtio/virtio_mmio.c).
>>
>> Thanks,
>>
>> Paolo
> That one uses weak barriers AFAIK.
>
> IIUC you mean rproc_virtio_notify.
>
> I suspect it works because specific kick callbacks have a barrier internally.
Yes, that one. At least keystone_rproc_kick doesn't seem to have a barrier.
Paolo