On Thu, Jan 09, 2020 at 11:55:18PM +0000, Nicholas Johnson wrote:
> On Thu, Jan 09, 2020 at 03:55:17PM -0600, Bjorn Helgaas wrote:
> > On Thu, Jan 09, 2020 at 06:31:57PM +0800, Yicong Yang wrote:
> > > On 2020/1/9 12:27, Bjorn Helgaas wrote:
> > > > [+cc Nicholas, who is working in this area]
> > > >
> > > > On Thu, Jan 09, 2020 at 11:35:09AM +0800, Yicong Yang wrote:
> > > >> Hi,
> > > >>
> > > >> recently I met a problem with pci bus resource allocation. The allocation strategy
> > > >> makes me confused and leads to a wrong allocation results.
> > > >>
> > > >> There is a hisilicon network device with four functions under one root port. The
> > > >> original bios resources allocation looks like:
> > > > What kernel is this? Can you collect the complete dmesg log?
> > >
> > > The kernel version is 5.4.0.
> >
> > Good; at least we know this isn't related to Nicholas' new resource
> > code that's in -next right now.
>
> It is not in next - it is in the release candidates, right?
There are a few things already in v5.5-rc5:
c13704f5685d ("PCI: Avoid double hpmemsize MMIO window assignment")
d7b8a217521c ("PCI: Add "pci=hpmmiosize" and "pci=hpmmioprefsize" parameters")
The following are currently in -next and should appear in v5.6-rc1:
ddbbbb6cb825 ("PCI: Allow extend_bridge_window() to shrink resource if necessary")
2b2108891303 ("PCI: Set resource size directly in extend_bridge_window()")
7bd85f16152b ("PCI: Rename extend_bridge_window() parameter")
5b55d9cf7d43 ("PCI: Consider alignment of hot-added bridges when distributing available resources")
I wanted to make sure Yicong was not testing -next.
Bjorn
