linux-kernel - Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <565E0FC6.9040209@oracle.com>
Date:	Tue, 1 Dec 2015 14:23:18 -0700
From:	Khalid Aziz <khalid.aziz@...cle.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	David Miller <davem@...emloft.net>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Wei Yang <weiyang@...ux.vnet.ibm.com>, TJ <linux@....tj>,
	Yijing Wang <wangyijing@...wei.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

On 11/23/2015 07:39 PM, Yinghai Lu wrote:
> On Mon, Nov 23, 2015 at 1:31 PM, Khalid Aziz <khalid.aziz@...cle.com> wrote:
>>> Looks like only the device BAR6 is not assigned form OF?
>>
>> Any progress on this? Do you need any more information from me?
>
> Should be one warning about this device in that system.
>
> We don't need to do anything about it if the device is working with
> this patch set.

Hi Yinghai,

Picking this up again after thanksgiving.......

The device does work with this patch. Doesn't this warning mean BAR6 
resources could not be reserved which means the device driver may not be 
able to get the BAR6 resource at some point if another device grabs the 
unreserved resource?

David M had pointed out an issue with how OF driver uses the same 
address range for all ROMs enabling them only one at a time. That seems 
to be in play here in the issue I am seeing. Does this patch series need 
to address this?

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