From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53493) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzisZ-0002F1-L0 for qemu-devel@nongnu.org; Wed, 25 Jun 2014 04:48:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WzisS-00081r-5m for qemu-devel@nongnu.org; Wed, 25 Jun 2014 04:48:31 -0400 Received: from mga09.intel.com ([134.134.136.24]:51036) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzisS-00081e-0p for qemu-devel@nongnu.org; Wed, 25 Jun 2014 04:48:24 -0400 Message-ID: <53AA8CC2.7090406@intel.com> Date: Wed, 25 Jun 2014 16:48:02 +0800 From: "Chen, Tiejun" MIME-Version: 1.0 References: <1403662641-28526-1-git-send-email-tiejun.chen@intel.com> <1403662641-28526-3-git-send-email-tiejun.chen@intel.com> <20140625064545.GB25563@redhat.com> <53AA8404.8040708@intel.com> <20140625082850.GB32652@redhat.com> <53AA8AAB.30100@intel.com> <20140625084347.GE32652@redhat.com> In-Reply-To: <20140625084347.GE32652@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [v5][PATCH 2/5] xen, gfx passthrough: create pseudo intel isa bridge List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: peter.maydell@linaro.org, xen-devel@lists.xensource.com, stefano.stabellini@eu.citrix.com, allen.m.kay@intel.com, qemu-devel@nongnu.org, Kelly.Zytaruk@amd.com, yang.z.zhang@intel.com, anthony@codemonkey.ws, anthony.perard@citrix.com, pbonzini@redhat.com On 2014/6/25 16:43, Michael S. Tsirkin wrote: > On Wed, Jun 25, 2014 at 04:39:07PM +0800, Chen, Tiejun wrote: >>> In fact it's exactly what passthrough does. >>> I wonder if more bits from ./hw/i386/kvm/pci-assign.c >>> can be reused. How do you poke at the host device? sysfs? >> >> Yes, sysfs. >> >> Thanks >> Tiejun > > Then you should be able to re-use large chunks of > ./hw/i386/kvm/pci-assign.c: basically everything > that deals with emulation. Do you mean those hooks to get info from the real device? Xen have its own wrapper, xen_host_pci_get_block(), so we always go there in xen scenario. Thanks Tiejun > > > >