linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ben Collins <bcollins@ubuntu.com>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] PPC: PCI: Fix pcibios_io_space_offset() so it works for 32-bit ptr/64-bit rsrcs
Date: Sat, 09 Jun 2012 08:48:51 +1000	[thread overview]
Message-ID: <1339195731.24838.53.camel@pasglop> (raw)
In-Reply-To: <BA42176E-B45B-4628-A143-EA7465233651@ubuntu.com>

On Fri, 2012-06-08 at 14:38 -0400, Ben Collins wrote:
> >> pci_bus 0000:00: root bus resource [io  0xffbeb000-0xffbfafff] (bus
> >> address [0x100000000-0x10000ffff])
> >> 
> >> I only have one PCIe RAID card on the bare metal system. Not
> >> surprising I never noticed the problem on it directly.
> > 
> > Can you show me the device-tree node for that PCI host bridge ?
> 
> 
> It's a p4080ds, so it's in arch/powerpc/boot/
> 
> And that means that this bug affects a real hardware platform, so I
> think it makes it more valid to include it. The only reason it didn't
> affect me directly is because my only PCIe card doesn't have io, just
> mem BARs. 

Something doesn't make sense. The bus address printed above are clearly
not right, the .dts contains for the "ranges" entries for IO space of
all 3 bridges:

  0x01000000 0 0x00000000 0xf 0xf8000000 0x0 0x00010000
  0x01000000 0 0x00000000 0xf 0xf8010000 0x0 0x00010000
  0x01000000 0 0x00000000 0xf 0xf8020000 0x0 0x00010000

So something is wrong with the printing of the bus address, there's a
stale top bit (overflow from the 64-bit substraction somewhere ?)

Cheers,
Ben.

  reply	other threads:[~2012-06-08 22:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  3:50 [PATCH] PPC: PCI: Fix pcibios_io_space_offset() so it works for 32-bit ptr/64-bit rsrcs Ben Collins
2012-06-06  5:15 ` Benjamin Herrenschmidt
2012-06-18 15:23   ` Bjorn Helgaas
2012-06-18 20:39     ` Benjamin Herrenschmidt
2012-06-18 21:04       ` Ben Collins
2012-06-18 22:45         ` Benjamin Herrenschmidt
2012-06-21  0:20       ` Bjorn Helgaas
2012-06-06 21:15 ` Scott Wood
2012-06-06 22:21   ` Benjamin Herrenschmidt
2012-06-07  0:37     ` Scott Wood
2012-06-06 23:35   ` Ben Collins
2012-06-07  9:30     ` Benjamin Herrenschmidt
2012-06-07 15:38       ` Ben Collins
2012-06-07 21:32         ` Benjamin Herrenschmidt
2012-06-08 18:38           ` Ben Collins
2012-06-08 22:48             ` Benjamin Herrenschmidt [this message]
2012-06-21  2:46 ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1339195731.24838.53.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=bcollins@ubuntu.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).