From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [v7][PATCH 06/16] hvmloader/pci: skip reserved ranges Date: Tue, 14 Jul 2015 12:50:07 +0100 Message-ID: <55A5138F0200007800090A71@mail.emea.novell.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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55A4EA54.60708@intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tiejun Chen 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 14.07.15 at 12:54, wrote: >>> I think bitmap mechanism is a good idea but honestly, its not easy to >>> cover all requirements here. And just like bootmem on Linux side, so its >>> a little complicated to implement this entirely. So I prefer not to >>> introduce this way in current phase. >> >> I'm afraid it's going to be hard to convince me of any approaches >> further complicating the current mechanism instead of overhauling >> it. > > I agree we'd better overhaul this since we already found something > unreasonable here. But one or two weeks is really not enough to fix this > with a bitmap framework, and although a bitmap can make mmio allocation > better, but more complicated if we just want to allocate PCI mmio. > > So could we do this next? I just feel if you'd like to pay more time > help me refine our current solution, its relatively realistic to this > case :) And then we can go into bitmap in details or work out a better > solution in sufficient time slot. Looking at how long it took to get here (wasn't this series originally even meant to go into 4.5?) and how much time I already spent reviewing all the previous versions, I don't see a point in wasting even more time on working out details of an approach that's getting too complex/ugly already anyway. Jan