From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Xen-devel] [v4][PATCH 2/5] xen,
 gfx passthrough: create intel isa bridge
Date: Tue, 03 Jun 2014 14:24:40 +0200
Message-ID: <538DBE88.2090607@redhat.com>
References: <1401440369-29929-1-git-send-email-tiejun.chen@intel.com>
	<1401440369-29929-3-git-send-email-tiejun.chen@intel.com>
	<538D8B59.4070105@redhat.com>
	<alpine.DEB.2.02.1406031203340.4779@kaball.uk.xensource.com>
	<538DB4B4.6000602@eu.citrix.com>
	<13644003.20140603142115@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <13644003.20140603142115@eikelenboom.it>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
To: Sander Eikelenboom <linux@eikelenboom.it>, George Dunlap <george.dunlap@eu.citrix.com>
Cc: peter.maydell@linaro.org, xen-devel@lists.xensource.com, Ian Campbell <Ian.Campbell@citrix.com>, mst@redhat.com, allen.m.kay@intel.com, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Kelly.Zytaruk@amd.com, qemu-devel@nongnu.org, anthony.perard@citrix.com, Tim Deegan <tim@xen.org>, Anthony Liguori <anthony@codemonkey.ws>, yang.z.zhang@intel.com, Tiejun Chen <tiejun.chen@intel.com>, George Dunlap <george.dunlap@citrix.com>, Konrad Rzeszutek Wilk <konrad@kernel.org>
List-Id: xen-devel@lists.xenproject.org

Il 03/06/2014 14:21, Sander Eikelenboom ha scritto:
>
> The last part should perhaps be fixed in the driver/firmware (for instance
> the assumption the device is always device 00:02.0, that's valid for real intel
> hardware, but not necessary for passthrough or emulation). A requirement for
> using the latest firmware/drivers for passthrough to work could be acceptable i
> guess ?

The problem is worse than that.  The assumptions are that the driver can 
make choices based on the device/vendor IDs of 00:1f.0, and that the 
driver can read/write to the config space of 00:00.0.

Paolo