From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [v7][PATCH 06/16] hvmloader/pci: skip reserved ranges Date: Wed, 15 Jul 2015 19:40:28 +0800 Message-ID: <55A646AC.1060000@intel.com> References: <1436420047-25356-1-git-send-email-tiejun.chen@intel.com> <1436420047-25356-7-git-send-email-tiejun.chen@intel.com> <55A3D5600200007800090330@mail.emea.novell.com> <55A4AE88.2000200@intel.com> <55A4F2270200007800090834@mail.emea.novell.com> <55A4EA54.60708@intel.com> <55A5138F0200007800090A71@mail.emea.novell.com> <55A5AF6F.1050305@intel.com> <55A5E122.7030203@intel.com> <55A6374E02000078000911EC@mail.emea.novell.com> <55A6210E.8080406@intel.com> <55A64386020000780009132E@mail.emea.novell.com> <55A65FD50200007800091475@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55A65FD50200007800091475@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , George Dunlap Cc: Wei Liu , Ian Campbell , Stefano Stabellini , Andrew Cooper , Ian Jackson , "xen-devel@lists.xen.org" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 2015/7/15 19:27, Jan Beulich wrote: >>>> On 15.07.15 at 13:05, wrote: >> This patch series as a whole represents a lot of work and a lot of >> tangible improvements to the situation; and (unless the situation has >> changed) it's almost entirely acked apart from the MMIO placement >> part. If there is a simple way that we can change hvmloader so that >> most (or even many) VM/device combinations work properly for the 4.6 >> release, then I think it's worth considering. > > And I think the simplest way is to replace the allocation mechanism This is the best way not the simplest way. The bitmap way matching our all requirement is not easy and realistic to address design/write/test/review in short time. And also the entire replacement would bring more potential risks to 4.6 release. Thanks Tiejun > as outlined rather than trying to make the current model cope with > the new requirement. > > Jan > > >