| 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
| ||
|
Message-ID: <473327A1.9080907@qumranet.com> Date: Thu, 08 Nov 2007 17:13:37 +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: >> If a pci device is capable of dma (or issuing interrupts), it will be >> useless with pv pci. > > Hrm, I think we may be talking about different things. Are you > thinking that the driver I posted allows you to do PCI pass-through > over virtio? That's not what it is. > > The driver I posted is a virtio implementation that uses a PCI > device. This lets you use virtio-blk and virtio-net under KVM. The > alternative to this virtio PCI device would be a virtio transport > built with hypercalls like lguest has. I choose a PCI device because > it ensured that each virtio device showed up like a normal PCI device. > > Am I misunderstanding what you're asking about? > No, I completely misunderstood the patch. Should review complete patches rather than random hunks. Sorry for the noise. -- 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