Re: [RFC PATCH 0/7] Untrusted device support for virtio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [RFC PATCH 0/7] Untrusted device support for virtio
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 22 Apr 2021 07:31:28 +0100
Cc: mst@xxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xieyongji@xxxxxxxxxxxxx, stefanha@xxxxxxxxxx, file@xxxxxxxxxxxxxxxxx, ashish.kalra@xxxxxxx, martin.radev@xxxxxxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx
In-reply-to: <20210421032117.5177-1-jasowang@redhat.com>
References: <20210421032117.5177-1-jasowang@redhat.com>

On Wed, Apr 21, 2021 at 11:21:10AM +0800, Jason Wang wrote:
> The behaivor for non DMA API is kept for minimizing the performance
> impact.

NAK.  Everyone should be using the DMA API in a modern world.  So
treating the DMA API path worse than the broken legacy path does not
make any sense whatsoever.

Follow-Ups:
- Re: [RFC PATCH 0/7] Untrusted device support for virtio
  - From: Jason Wang

References:
- [RFC PATCH 0/7] Untrusted device support for virtio
  - From: Jason Wang

Prev by Date: linux-next: build failure after merge of the cgroup tree
Next by Date: Re: linux-next: manual merge of the cgroup tree with the kvm tree
Previous by thread: [RFC PATCH 5/7] virtio_ring: introduce virtqueue_desc_add_split()
Next by thread: Re: [RFC PATCH 0/7] Untrusted device support for virtio
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux