| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 08 Nov 2007 16:37:59 +0200 From: Avi Kivity <avi@...ranet.com> To: Anthony Liguori <aliguori@...ibm.com> CC: linux-kernel@...r.kernel.org, Rusty Russell <rusty@...ycorp.com.au>, virtualization@...ts.osdl.org, kvm-devel@...ts.sourceforge.net Subject: Re: [kvm-devel] [PATCH 3/3] virtio PCI device Anthony Liguori wrote: > Avi Kivity wrote: >> Anthony Liguori wrote: >> >>> This is a PCI device that implements a transport for virtio. It >>> allows virtio >>> devices to be used by QEMU based VMMs like KVM or Xen. >>> >>> >> >> Didn't see support for dma. > > Not sure what you're expecting there. Using dma_ops in virtio_ring? > If a pci device is capable of dma (or issuing interrupts), it will be useless with pv pci. >> I think that with Amit's pvdma patches you >> can support dma-capable devices as well without too much fuss. >> > > What is the use case you're thinking of? A semi-paravirt driver that > does dma directly to a device? No, an unmodified driver that, by using clever tricks with dma_ops, can do dma directly to guest memory. See Amit's patches. In fact, why do a virtio transport at all? It can be done either with trap'n'emulate, or by directly mapping the device mmio space into the guest. (what use case are you considering? devices without interrupts and dma? pci door stoppers?) -- error compiling committee.c: too many arguments to function - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists