Re: sparc64 PCI BAR allocation is still problematic

From: Meelis Roos <mroos@linux.ee>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
	linux-pci@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: sparc64 PCI BAR allocation is still problematic
Date: Wed, 11 Apr 2018 17:40:41 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1804111738260.18432@math.ut.ee> (raw)
In-Reply-To: <20180411133334.GA91792@bhelgaas-glaptop.roam.corp.google.com>

> On Wed, Apr 11, 2018 at 10:59:19AM +0300, Meelis Roos wrote:
> > > Oops, sorry, I can't easily compile test it.  Here's an updated patch:
> > > 
> > > commit a9ded309cbf3f57e9979848fd0aa0ffacdf11f1a
> > > Author: Bjorn Helgaas <bhelgaas@google.com>
> > > Date:   Tue Apr 10 08:47:34 2018 -0500
> > 
> > Thanks, this patch compiles and works - Video RAM related BAR allocation 
> > errors are gone.
> 
> Great, thanks!  I didn't mean to take up so much of your time testing
> *all* of your systems :)

Well, they compiled in parallel :)

> > Hera are the /proc/iomem's but unfortunately the physical 
> > addresses have been censored by security:
> 
> If you look at /proc/iomem as root, you should see the actual
> addresses.

Yes, that was it.

> If you have any systems with VGA, it would be useful to test one of
> them.  

This is Blade 100, with atyfb frame buffer:

# cat /proc/iomem 
00000000-7effdfff : System RAM
  00404000-0085aadf : Kernel code
  0085aae0-009b8a8f : Kernel data
  009f2000-00a37a37 : Kernel bss
7f000000-7fee5fff : System RAM
7ff04000-7ff0bfff : System RAM
1ff00000000-1ffffffffff : /pci@1f,0
  1ff00000000-1ff000fffff : 0000:00:07.0
  1ff00400000-1ff0041ffff : 0000:00:0c.1
    1ff00400000-1ff0041ffff : sungem
  1ff00420000-1ff00421fff : 0000:00:0c.2
  1ff00422000-1ff00423fff : 0000:00:0c.2
  1ff00424000-1ff00425fff : 0000:00:08.0
  1ff00426000-1ff00427fff : 0000:00:13.0
  1ff00440000-1ff0045ffff : 0000:00:13.0
  1ff00800000-1ff00bfffff : 0000:00:0c.1
  1ff00c00000-1ff00ffffff : 0000:00:0c.2
  1ff01000000-1ff013fffff : 0000:00:0c.3
  1ff02000000-1ff02ffffff : 0000:00:0c.3
    1ff02000000-1ff02ffffff : ohci_hcd
  1ff03000000-1ff030fffff : PCI Bus 0000:01
    1ff03000000-1ff03001fff : 0000:01:00.0
      1ff03000000-1ff03001fff : sym53c8xx
    1ff03002000-1ff03003fff : 0000:01:02.0
    1ff03010000-1ff0301ffff : 0000:01:02.0
  1ff04000000-1ff04ffffff : 0000:00:13.0
    1ff04000000-1ff04ffffff : atyfb
  1ffc0000000-1ffdfffffff : IOMMU
  1fff1000000-1fff1001fff : eeprom

> I took a quick look through your lspci logs, and it *looks* like the
> Blade 100 has a VGA at 00:13.0, but I don't see the "Video RAM area"
> entry in /proc/iomem that I expected:
> 
> > Blade 100: Video RAM related BAR error is gnone, this is still here:
> > [    6.131499] pci 0000:00:07.0: can't claim BAR 0 [io  0x1fe02000000-0x1fe0200ffff]: address conflict with 0000:00:03.0 [io  0x1fe02000600-0x1fe0200061f]
> > 
> > 00000000-00000000 : System RAM
> >   00000000-00000000 : Kernel code
> >   00000000-00000000 : Kernel data
> >   00000000-00000000 : Kernel bss
> > 00000000-00000000 : System RAM
> > 00000000-00000000 : System RAM
> > 00000000-00000000 : /pci@1f,0
> >   00000000-00000000 : 0000:00:07.0
> >   00000000-00000000 : 0000:00:0c.1
> >     00000000-00000000 : sungem
> >   00000000-00000000 : 0000:00:0c.2
> >   00000000-00000000 : 0000:00:0c.2
> >   00000000-00000000 : 0000:00:08.0
> >   00000000-00000000 : 0000:00:13.0
> >   00000000-00000000 : 0000:00:13.0
> >   00000000-00000000 : 0000:00:0c.1
> >   00000000-00000000 : 0000:00:0c.2
> >   00000000-00000000 : 0000:00:0c.3
> >   00000000-00000000 : 0000:00:0c.3
> >     00000000-00000000 : ohci_hcd
> >   00000000-00000000 : PCI Bus 0000:01
> >     00000000-00000000 : 0000:01:00.0
> >       00000000-00000000 : sym53c8xx
> >     00000000-00000000 : 0000:01:02.0
> >     00000000-00000000 : 0000:01:02.0
> >   00000000-00000000 : 0000:00:13.0
> >     00000000-00000000 : atyfb
> >   00000000-00000000 : IOMMU
> >   00000000-00000000 : eeprom
> 

-- 
Meelis Roos (mroos@linux.ee)