From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB6Ul-0005uP-Gi for qemu-devel@nongnu.org; Tue, 04 Oct 2011 11:01:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RB6Uk-0005RC-8I for qemu-devel@nongnu.org; Tue, 04 Oct 2011 11:01:23 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:42647) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB6Uk-0005Qz-3g for qemu-devel@nongnu.org; Tue, 04 Oct 2011 11:01:22 -0400 Received: by qadb10 with SMTP id b10so516473qad.4 for ; Tue, 04 Oct 2011 08:01:21 -0700 (PDT) Message-ID: <4E8B1FBC.2080904@codemonkey.ws> Date: Tue, 04 Oct 2011 10:01:16 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1317739882-4809-1-git-send-email-anthony.perard@citrix.com> <4E8B1F0D.4080203@redhat.com> In-Reply-To: <4E8B1F0D.4080203@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Xen-devel] [PATCH RFC V1 00/11] Xen PCI Passthrough List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony PERARD , Alex Williamson , Xen Devel , QEMU-devel , Stefano Stabellini On 10/04/2011 09:58 AM, Avi Kivity wrote: > On 10/04/2011 04:51 PM, Anthony PERARD wrote: >> Hi all, >> >> This patch series introduce the PCI passthrough for Xen. >> >> First, we have HostPCIDevice that help to access one PCI device of the host. >> >> Then, there are several additions in the QEMU code. One is qemu_run_one_timer >> to run a specific timer. It is used by PCI passthrough to run a timer about >> power management. Another is pci_check_bar_overlap. >> >> There are also several change in pci_ids and pci_regs. >> >> Last part, but not least, the PCI passthrough device himself. Cut in 3 parts >> (or file), there is one to take care of the initialisation of a passthrough >> device. The second one handle everything about the config address space, there >> are specifics functions for every config register. The third one is to handle >> MSI. >> >> I'm still working on setting a PCI passthrough device through QMP from libxl >> (xen tool stack). It is just a call to device_add, with the driver parametter >> hostaddr="0000:00:1b.0". >> >> There is some minor things missing: >> - copyright header >> - PCI IO space multiplexer >> >> > > We also have pci passthrough in qemu-kvm (I think based on the same Neocleus > code). Rather than having two pci assignment implementations, I think we should > have just one, with the differences (programming the hypervisor) abstracted at > that level. I agree in principle but how close is qemu-kvm pci passthrough to a mergable state? Would it make sense to merge the Xen code first and then abstract it? Regards, Anthony Liguori >