[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVSK9kAg-qyASpb1AoHSwQbKK33eHhFmzUjoLOftK9M4w@mail.gmail.com>
Date: Wed, 8 Jul 2015 22:01:47 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Wei Yang <weiyang@...ux.vnet.ibm.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
David Miller <davem@...emloft.net>,
David Ahern <david.ahern@...cle.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
TJ <linux@....tj>, Yijing Wang <wangyijing@...wei.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 36/36] PCI: Don't set flags to 0 when assign resource fail
On Wed, Jul 8, 2015 at 8:30 PM, Wei Yang <weiyang@...ux.vnet.ibm.com> wrote:
> Hi, Yinghai
>
> This patch may introduce some problem.
>
> On my P8 machine, after applying this patch, I see following error:
>
> [ 0.589948] pnv_ioda_setup_pe_seg: trigger IO SEG 0
> [ 0.589992] pnv_ioda_setup_pe_seg: res[io 0x1000-0x3fff] 100
>
> The last 0x100 is the res->flags, which indicates the UNSET and DISABLED bit
> is not set.
Maybe we should introduce resource_disabled() for that.
Please check if attached patch would fix the problem.
Thanks
Yinghai
View attachment "resource_disabled.patch" of type "text/x-patch" (17812 bytes)
Powered by blists - more mailing lists