Re: [PATCH] PCI: Clear bridge MEM_64 flag if one child does not support it

[Marek KordÃk]

On 12/09/2014 08:20 AM, Yinghai Lu wrote:
> On Mon, Dec 8, 2014 at 6:26 PM, Wei Yang <weiyang@xxxxxxxxxxxxxxxxxx> wrote:
> > On Tue, Dec 09, 2014 at 11:11:19AM +1100, Gavin Shan wrote:
> > > I'm going to give it a spin and Richard, could you please apply Yinghai's
> > > patch to see if your SRIOV code can work properly?
> >
> > I did a quick test on my machine. This patch doesn't affect the MMIO
> > allocation on out platform, so SRIOV works fine.
> >
> > I will spend more time to read the patch to get more understanding about the
> > problem.
>
> Hi Marek,
>
> Can you boot following branch with "debug ignore_loglevel pci=realloc"
> on your setup?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-pci-allocate-fit-3.18
>
> it has
> 8f74af9: PCI, x86: Allocate mmio near end of free range
> 1ff91c1: PCI: Don't allocate small resource in big free space.
> 108b43b: resources: Add allocate_resource_fit()
> b6a22f0: resources: Make find_resource could return just fit resource
> cf50e16: resources: Split out __allocate_resource()
>
> on top the v3.18, and it will allocate resource in fit way.
>
> Thanks
>
> Yinghai
Hi Yinghai,

I have built and booted your branch and it works well. Do you want me to 
attach some logs?
(I am new here and I have read http://www.tux.org/lkml/ and I don't want 
to break some rules for attachment size)

Marek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/