[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79dde4e9-3134-e444-83a1-d1012f7a0384@oracle.com>
Date: Wed, 21 Feb 2018 13:37:45 -0700
From: Khalid Aziz <khalid.aziz@...cle.com>
To: Bjorn Helgaas <helgaas@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Cc: sparclinux@...r.kernel.org, linux-pci@...r.kernel.org,
Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org,
David Ahern <david.ahern@...cle.com>, TJ <linux@....tj>
Subject: Re: [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups
On 02/20/2018 04:39 PM, Bjorn Helgaas wrote:
>
> Both these patches are on my pci/sparc branch and appeared in the
> Feb 19 linux-next tree.
>
> Any testing and feedback (especially on the second patch, which should
> change /proc/iomem) would be great.
>
> They're headed for v4.17 unless I hear about issues.
>
> It would be useful to hear about what's still broken so I can try to
> pull in the other patches.
>
Hi Bjorn,
I tested these two patches on an M7 machine. With these two patches, one
of the PCI devices was able to claim BAR 0 which it fails to without
these patches. This device happens to be a NIC, so with these two
patches, the NIC finally works on my test machine. I have attached log
showing all the failures to claim a BAR. First file is from 4.16-rc2
while the second one is from 4.16-rc2+these two patches. There still are
a number of failures to claim BAR even with these two patches.
I am also attaching /proc/iomem for the 4.16-rc2 kernel and 4.16-rc2
with these two patches.
--
Khalid
View attachment "log.rc2" of type "text/plain" (1831 bytes)
View attachment "log.rc2-bjorn" of type "text/plain" (2129 bytes)
View attachment "iomem.rc2" of type "text/plain" (3488 bytes)
View attachment "iomem.rc2-bjorn" of type "text/plain" (3475 bytes)
Powered by blists - more mailing lists