From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X2InE-00038F-Lv for qemu-devel@nongnu.org; Wed, 02 Jul 2014 07:33:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X2In5-00045A-G4 for qemu-devel@nongnu.org; Wed, 02 Jul 2014 07:33:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24308) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X2In5-00044m-4V for qemu-devel@nongnu.org; Wed, 02 Jul 2014 07:33:31 -0400 Message-ID: <53B3EDF5.4000802@redhat.com> Date: Wed, 02 Jul 2014 13:33:09 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <53ABE551.3080407@intel.com> <53ABF00E.6000309@redhat.com> <53B0D0C5.60000@intel.com> <20140630064822.GB14491@redhat.com> <53B110CA.6070606@intel.com> <20140630090511.GB15777@redhat.com> <53B1BAF9.6040800@citrix.com> <20140701053907.GA6108@redhat.com> <20140701170206.GB7640@redhat.com> <53B2F238.7000009@citrix.com> In-Reply-To: <53B2F238.7000009@citrix.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Xen-devel] [v5][PATCH 0/5] xen: add Intel IGD passthrough support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ross Philipson , "Michael S. Tsirkin" , Stefano Stabellini Cc: "peter.maydell@linaro.org" , "xen-devel@lists.xensource.com" , "Allen M. Kay" , "Kelly.Zytaruk@amd.com" , "qemu-devel@nongnu.org" , Anthony Perard , "anthony@codemonkey.ws" , "yang.z.zhang@intel.com" , "Chen, Tiejun" Il 01/07/2014 19:39, Ross Philipson ha scritto: > > We do IGD pass-through in our project (XenClient). The patches > originally came from our project. We surface the same ISA bridge and > have never had activation issues on any version of Widows from XP to > Win8. We do not normally run server platforms so I can't say for sure > there. The problem is not activation, the problem is that the patches are making assumptions on the driver and the firmware that might work today but are IMHO just not sane. I would have no problem with a clean patchset that adds a new machine type and doesn't touch code in "-M pc", but it looks like mst disagrees. Ultimately, if a patchset is too hacky for upstream, you can include it in your downstream XenClient (and XenServer) QEMU branch. It happens. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Xen-devel] [v5][PATCH 0/5] xen: add Intel IGD passthrough support Date: Wed, 02 Jul 2014 13:33:09 +0200 Message-ID: <53B3EDF5.4000802@redhat.com> References: <53ABE551.3080407@intel.com> <53ABF00E.6000309@redhat.com> <53B0D0C5.60000@intel.com> <20140630064822.GB14491@redhat.com> <53B110CA.6070606@intel.com> <20140630090511.GB15777@redhat.com> <53B1BAF9.6040800@citrix.com> <20140701053907.GA6108@redhat.com> <20140701170206.GB7640@redhat.com> <53B2F238.7000009@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53B2F238.7000009@citrix.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Ross Philipson , "Michael S. Tsirkin" , Stefano Stabellini Cc: "peter.maydell@linaro.org" , "xen-devel@lists.xensource.com" , "Allen M. Kay" , "Kelly.Zytaruk@amd.com" , "qemu-devel@nongnu.org" , Anthony Perard , "anthony@codemonkey.ws" , "yang.z.zhang@intel.com" , "Chen, Tiejun" List-Id: xen-devel@lists.xenproject.org Il 01/07/2014 19:39, Ross Philipson ha scritto: > > We do IGD pass-through in our project (XenClient). The patches > originally came from our project. We surface the same ISA bridge and > have never had activation issues on any version of Widows from XP to > Win8. We do not normally run server platforms so I can't say for sure > there. The problem is not activation, the problem is that the patches are making assumptions on the driver and the firmware that might work today but are IMHO just not sane. I would have no problem with a clean patchset that adds a new machine type and doesn't touch code in "-M pc", but it looks like mst disagrees. Ultimately, if a patchset is too hacky for upstream, you can include it in your downstream XenClient (and XenServer) QEMU branch. It happens. Paolo