[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200429103438.GF5097@quicinc.com>
Date: Wed, 29 Apr 2020 16:04:40 +0530
From: Srivatsa Vaddagiri <vatsa@...eaurora.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Lu Baolu <baolu.lu@...ux.intel.com>, tsoni@...eaurora.org,
virtio-dev@...ts.oasis-open.org, konrad.wilk@...cle.com,
jan.kiszka@...mens.com, jasowang@...hat.com,
christoffer.dall@....com,
virtualization@...ts.linux-foundation.org, alex.bennee@...aro.org,
iommu@...ts.linux-foundation.org, stefano.stabellini@...inx.com,
will@...nel.org, linux-kernel@...r.kernel.org,
pratikp@...eaurora.org
Subject: Re: [PATCH 5/5] virtio: Add bounce DMA ops
* Michael S. Tsirkin <mst@...hat.com> [2020-04-29 06:20:48]:
> On Wed, Apr 29, 2020 at 03:39:53PM +0530, Srivatsa Vaddagiri wrote:
> > That would still not work I think where swiotlb is used for pass-thr devices
> > (when private memory is fine) as well as virtio devices (when shared memory is
> > required).
>
> So that is a separate question. When there are multiple untrusted
> devices, at the moment it looks like a single bounce buffer is used.
>
> Which to me seems like a security problem, I think we should protect
> untrusted devices from each other.
I think as first step, let me see if we can make swiotlb driver accept a target
memory segment as its working area. That may suffice our needs I think. A
subsequent step could be to make swiotlb driver recognize multiple pools.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
Powered by blists - more mailing lists