On Tue, 20 Oct 2020 09:18:48 +0300
"Kirill A. Shutemov" wrote:
> VirtIO for KVM is a primary way to provide IO. All memory that used for
> communication with the host has to be marked as shared.
>
> The easiest way to archive that is to use DMA API that already knows how
> to deal with shared
On Tue, Oct 20, 2020 at 09:06:58AM +0100, Christoph Hellwig wrote:
> NAK. Any virtio implementation that needs special DMA OPS treatment
> needs to set the VIRTIO_F_ACCESS_PLATFORM bit. The only reason the
> Xen hack existst is because it slipped in a long time ago and we can't
> fix that any
NAK. Any virtio implementation that needs special DMA OPS treatment
needs to set the VIRTIO_F_ACCESS_PLATFORM bit. The only reason the
Xen hack existst is because it slipped in a long time ago and we can't
fix that any more.
VirtIO for KVM is a primary way to provide IO. All memory that used for
communication with the host has to be marked as shared.
The easiest way to archive that is to use DMA API that already knows how
to deal with shared memory.
Signed-off-by: Kirill A. Shutemov
---
4 matches
Mail list logo