search for: _dma

...would not be doing address mapping. > > > > rpmsg uses virtio, but it's with a twist: they're not talking to a > > host. Thus my preference, in order, would be: > > > > 1) Don't use non-kmalloc addresses. > > 2) If that's not possible, call these _dma interfaces _rpmsg instead, > > so normal virtio users don't get confused and try to use them. > > Thanks Rusty, > > That was helpful, I'll see if I can do something in line with nr 2. > > AFAICT, #1 will be hard. The remote-processor would have to be > cache-co...

...would not be doing address mapping. > > > > rpmsg uses virtio, but it's with a twist: they're not talking to a > > host. Thus my preference, in order, would be: > > > > 1) Don't use non-kmalloc addresses. > > 2) If that's not possible, call these _dma interfaces _rpmsg instead, > > so normal virtio users don't get confused and try to use them. > > Thanks Rusty, > > That was helpful, I'll see if I can do something in line with nr 2. > > AFAICT, #1 will be hard. The remote-processor would have to be > cache-co...

...cided some time ago that as we're paravirtualized, we would not be doing address mapping. rpmsg uses virtio, but it's with a twist: they're not talking to a host. Thus my preference, in order, would be: 1) Don't use non-kmalloc addresses. 2) If that's not possible, call these _dma interfaces _rpmsg instead, so normal virtio users don't get confused and try to use them. Cheers, Rusty. > --- > drivers/rpmsg/virtio_rpmsg_bus.c | 28 ++++++++++++++++++++++------ > 1 file changed, 22 insertions(+), 6 deletions(-) > > diff --git a/drivers/rpmsg/virtio_rpm...

...cided some time ago that as we're paravirtualized, we would not be doing address mapping. rpmsg uses virtio, but it's with a twist: they're not talking to a host. Thus my preference, in order, would be: 1) Don't use non-kmalloc addresses. 2) If that's not possible, call these _dma interfaces _rpmsg instead, so normal virtio users don't get confused and try to use them. Cheers, Rusty. > --- > drivers/rpmsg/virtio_rpmsg_bus.c | 28 ++++++++++++++++++++++------ > 1 file changed, 22 insertions(+), 6 deletions(-) > > diff --git a/drivers/rpmsg/virtio_rpm...

...ping. > > > > > > rpmsg uses virtio, but it's with a twist: they're not talking to a > > > host. Thus my preference, in order, would be: > > > > > > 1) Don't use non-kmalloc addresses. > > > 2) If that's not possible, call these _dma interfaces _rpmsg instead, > > > so normal virtio users don't get confused and try to use them. > > > > Thanks Rusty, > > > > That was helpful, I'll see if I can do something in line with nr 2. > > > > AFAICT, #1 will be hard. The remote-proce...

...re > paravirtualized, we would not be doing address mapping. > > rpmsg uses virtio, but it's with a twist: they're not talking to a > host. Thus my preference, in order, would be: > > 1) Don't use non-kmalloc addresses. > 2) If that's not possible, call these _dma interfaces _rpmsg instead, > so normal virtio users don't get confused and try to use them. Thanks Rusty, That was helpful, I'll see if I can do something in line with nr 2. AFAICT, #1 will be hard. The remote-processor would have to be cache-coherent and share memory address-space...

From: "Edgar E. Iglesias" <edgar.iglesias at xilinx.com> I'm trying to run rpmsg and remoteproc on the ZynqMP (arm64) but I'm hitting a DMA/mm error. The issue was discussed here: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/333050.html Russel King pointed out that the arm64 is not doing anything wrong by returning vmapped memory (which is incompatible

From: "Edgar E. Iglesias" <edgar.iglesias at xilinx.com> I'm trying to run rpmsg and remoteproc on the ZynqMP (arm64) but I'm hitting a DMA/mm error. The issue was discussed here: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/333050.html Russel King pointed out that the arm64 is not doing anything wrong by returning vmapped memory (which is incompatible