[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [v3][PATCH 07/16] hvmloader/pci: skip reserved ranges
On 2015/6/17 17:02, Jan Beulich wrote: On 17.06.15 at 10:26, <tiejun.chen@xxxxxxxxx> wrote:Something hits me to generate another idea, #1. Still allocate all devices as before. #2. Lookup all actual bars to check if they're conflicting RMRR We can skip these bars to keep zero. Then later it would make lookup easily. #3. Need to reallocate these conflicting bars. #3.1 Trying to reallocate them with the remaining resources #3.2 If the remaining resources aren't enough, we need to allocate them from high_mem_resource.That's possible onyl for 64-bit BARs. You're right so this means its not proper to adjust mmio_total to include conflicting reserved ranges and finally moved all conflicting bars to high_mem_resource as Kevin suggested previously, so i high level, we still need to decrease pci_mem_start to populate more RAM to compensate them as I did, right? I just feel this way may be easy and better. And even, this way also can help terminate the preexisting allocation failures, right?I think this complicates things rather than simplifying them: The more passes (and adjustments to previous settings) you do, the more error prone the whole logic will become. It may well be that you need to basically re-write what is there right now... Yeah, we need to think about this carefully. Thanks Tiejun _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |