From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDjG5-0006YU-Ge for qemu-devel@nongnu.org; Tue, 22 Mar 2005 08:17:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDjG3-0006XY-D5 for qemu-devel@nongnu.org; Tue, 22 Mar 2005 08:17:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDjEb-0005nb-9b for qemu-devel@nongnu.org; Tue, 22 Mar 2005 08:15:49 -0500 Received: from [213.146.130.142] (helo=trantor.org.uk) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1DDiU5-0007UN-79 for qemu-devel@nongnu.org; Tue, 22 Mar 2005 07:27:45 -0500 Subject: Re: [Qemu-devel] pciproxy status? From: Gianni Tedesco In-Reply-To: <423FF1CA.3000406@nixia.no> References: <423FF1CA.3000406@nixia.no> Content-Type: text/plain Date: Tue, 22 Mar 2005 12:25:45 +0000 Message-Id: <1111494345.4238.75.camel@sherbert> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, 2005-03-22 at 11:22 +0100, Karsten N. Strand wrote: >Hi, >First I must say that I'm extremely impressed with the development of >qemu, and that I think it's currently one of the most technical >interesting open source projects these days. Then the question.. > >What's the status of the pciproxy patch? Is it still work in progress, >or have it stalled now? What about pci DMA support? Unfortunately it's pretty much stalled due to lack of time. It should work OK though provided your PCI device is not sharing IRQs. PCI DMA is somewhat tricky to implement (not possible in a general way without either patching the guest, or invasive patching of the host). Maybe by analyzing the logs thus far, you could build some device specific hooks for figuring out when/how to initiate DMA. I know the gelato team have got some patches that add new syscalls to linux for allocating buffers to userspace suitable for PCI DMA - which is the next thing thats required once you have the address/length of the buffers and direction of transfer. -- // Gianni Tedesco (gianni at scaramanga dot co dot uk) lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import