From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asZmi-0002Sp-V1 for qemu-devel@nongnu.org; Tue, 19 Apr 2016 13:50:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1asZmi-0002RH-4A for qemu-devel@nongnu.org; Tue, 19 Apr 2016 13:50:00 -0400 Date: Tue, 19 Apr 2016 20:49:48 +0300 From: "Michael S. Tsirkin" Message-ID: <20160419204907-mutt-send-email-mst@redhat.com> References: <1460994701.3765.23.camel@infradead.org> <20160418190203-mutt-send-email-mst@redhat.com> <1461004173.3765.73.camel@infradead.org> <20160419130732-mutt-send-email-mst@redhat.com> <20160419190520-mutt-send-email-mst@redhat.com> <20160419191914-mutt-send-email-mst@redhat.com> <1461083204.20056.8.camel@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <1461083204.20056.8.camel@infradead.org> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH RFC] fixup! virtio: convert to use DMA api List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Woodhouse Cc: Andy Lutomirski , "qemu-devel@nongnu.org Developers" , "linux-kernel@vger.kernel.org" , Paolo Bonzini , peterx@redhat.com, Cornelia Huck , Stefan Hajnoczi , Kevin Wolf , Amit Shah , qemu-block@nongnu.org, Jason Wang , Alex Williamson , Andy Lutomirski , Christian Borntraeger , Wei Liu , Linux Virtualization , kvm list On Tue, Apr 19, 2016 at 12:26:44PM -0400, David Woodhouse wrote: > On Tue, 2016-04-19 at 19:20 +0300, Michael S. Tsirkin wrote: > >=20 > > > I thought that PLATFORM served that purpose.=A0 Woudn't the host > > > advertise PLATFORM support and, if the guest doesn't ack it, the ho= st > > > device would skip translation?=A0 Or is that problematic for vfio? > >=20 > > Exactly that's problematic for security. > > You can't allow guest driver to decide whether device skips security. >=20 > Right. Because fundamentally, this *isn't* a property of the endpoint > device, and doesn't live in virtio itself. >=20 > It's a property of the platform IOMMU, and lives there. It's a property of the hypervisor virtio implementation, and lives there. --=20 MST