From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Discussion on whether to continue with the patches for Xen 4.5 Re: [v6][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Date: Mon, 29 Sep 2014 12:16:44 +0300 Message-ID: <20140929091644.GF12451@reaktio.net> References: <542017E80200007800036D1E@mail.emea.novell.com> <5420D357.1060202@intel.com> <5422A08C020000780003814F@mail.emea.novell.com> <5423E98E0200007800038C27@mail.emea.novell.com> <20140925141215.GC20089@laptop.dumpdata.com> <54244D7402000078000390F2@mail.emea.novell.com> <20140926135529.GG30097@laptop.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Zhang, Yang Z" Cc: "Tian, Kevin" , "G.R." , "xen-devel@lists.xen.org" , "paul.durrant@citrix.com" , Jan Beulich , "Chen, Tiejun" List-Id: xen-devel@lists.xenproject.org On Mon, Sep 29, 2014 at 01:26:52AM +0000, Zhang, Yang Z wrote: > > > but I could be very well mistaken - please correct me) would have to > > answer/fix all the patches in the next two working days. > > > > With the first RC going out on October 15th, that means a total of four > > working days to get all of this done, reviewed, fixed, and tested. > > > > And working under stress to get this done can mean introducing > > subtle bugs (this is based on my personal experience, so your > > experience might be different). > > > > Anyhow, I really need to know if - are all of the code pieces > > (minus the patches we are discussing) for this full GPU > > functionality in the Xen codebase and will it work with Xen 4.5 > > or will it require extra additional patches? And also, can > > Qemu-traditional + Xen 4.5 + RMRR patchset will work. > Speaking of qemu-traditional.. can you please check this (unapplied) patch: "[PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci cap on host bridge.": http://lists.xenproject.org/archives/html/xen-devel/2013-02/msg00538.html And some discussion/comments about it: http://lists.xen.org/archives/html/xen-devel/2013-07/msg01385.html That patch has been floating around for over 1,5 years, so it would be nice to get it cleaned up and applied finally.. based on the description it sounds like it's necessary to fix windows BSOD on certain Intel IGD hardware / drivers. -- Pasi