Re: Resource assignment oddities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 23, 2013 at 1:13 AM, Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> wrote:
> On Wed, May 22, 2013 at 01:50:35PM -0700, Yinghai Lu wrote:
>>On Wed, May 22, 2013 at 9:59 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
>>> We try must+optional as first, then if there is any ioport or mmio fail
>>> we will stick to must only then extend must to meet optional.
>>> but mmio range and mmio-pref could be connected each other,
>>> so extend will fail...
>>>
>>> problem here, some root bus will not have ioport range, so it will always have
>>> ioport allocation fail.
>>>
>>> looks like right fix for v3.9 should be as attached patch.
>>> it will keep must+optional for mmio, if only ioport fails....
>>
>>looks like i missed change to realloc_head list.
>>
>>Ben/Shan, can you check attached v2?
>>
>
> Sorry for late response. I spend lots of time to get the simulator working
> with PCI stuff. I had a try with your patch on top of mainline (3.10.RC2).
> Things look good except that we still see the intended the failure message
> of failure to assign I/O ports as the attached kernel log indicates :-)
>

Good, will resend this as complete form to Bjorn for v3.10.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux