From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJ7Dd-0003yM-75 for qemu-devel@nongnu.org; Mon, 09 Sep 2013 15:33:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VJ7DT-000319-Rh for qemu-devel@nongnu.org; Mon, 09 Sep 2013 15:33:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24716) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJ7DT-00030x-J5 for qemu-devel@nongnu.org; Mon, 09 Sep 2013 15:33:43 -0400 Date: Mon, 9 Sep 2013 22:35:47 +0300 From: "Michael S. Tsirkin" Message-ID: <20130909193547.GE2674@redhat.com> References: <20130909163422.GI1930@redhat.com> <522DFD61.10506@siemens.com> <522E00CE.9050400@siemens.com> <522E0514.1070803@siemens.com> <522E0E17.2050700@siemens.com> <522E0F4D.8090007@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <522E0F4D.8090007@redhat.com> Subject: Re: [Qemu-devel] [PATCH RFC v2 2/2] hw/pci: handle unassigned pci addresses List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Jan Kiszka , Anthony Liguori , Marcel Apfelbaum , QEMU Developers , Peter Maydell On Mon, Sep 09, 2013 at 08:11:25PM +0200, Paolo Bonzini wrote: > Il 09/09/2013 20:06, Jan Kiszka ha scritto: > > archive, was in the context of lock-less MMIO dispatching), and the > > consensus back then was that device-to-device DMA is generally a bug > > that is not worth supporting in all its beauty. But if you know a > > concrete scenario / guest where it matters, that would bring in a new > > aspect. > > Well, one I know is > > 10 SCREEN 1 > 20 COLOR 1: CIRCLE (160, 100), 80 > 30 PRINT "Hello QEMU!" > 40 DEF SEG=&hB800 > 50 BSAVE "FOO.PIC", 16000 > RUN > > Not sure if that counts as something that matters, or even if it works > right now with virtio-blk. > > Paolo I don't think it matters for virtio - it's a PV device and we can reasonably limit what works and what doesn't work there. It makes some sense for assigned devices (I think VFIO supports this to some extent) and we might at some point start emulating devices that do this. But mostly it's a driver bug, and all we need to do is make sure it doesn't cause security issues. -- MST