Thread (3 messages) flat view 3 messages, 2 authors, 2012-02-27

Re: linux-next: build failure after merge of the final tree

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2012-02-27 23:30:42
Also in: linuxppc-dev, lkml

On Mon, 2012-02-27 at 20:19 +1100, Benjamin Herrenschmidt wrote:
On Mon, 2012-02-27 at 17:37 +1100, Stephen Rothwell wrote:
quoted
        pci_add_resource_offset(resources, res,
-                       (resource_size_t) hose->io_base_virt - _IO_BASE);
+                       (resource_size_t)(unsigned long)hose->io_base_virt - _IO_BASE);
We have to be careful here as we do want sign extension to happen (yeah
it's odd, but it's the way we do IOs on ppc32 :-) Maybe I should change
it one day).

So we probably want to do:

	 (resource_size_t)(long long)(hose->io_base_virt - _IO_BASE)
Oops ... that was meant to read (long) not (long long)... Any ways, I
more or less convinced myself that even without the sign extension it
would still work, since the IO port number is eventually cast to an
unsigned int by the accessors, so as long as the low 32-bits are correct
(and they'll be with or without the sign extension), we should be fine.
It's just that something trying to print the resource might end up
displaying garbage in the top bits.

Cheers,
Ben.

Basically, IO resources are relative to _IO_BASE which on ppc32 is
basically the virtual address where we map the first PHB IO space.

Subsequent PHB mappings can end up below _IO_BASE, leading to negative
resource values for IO BARs on those busses. It all works fine because
even an unsigned addition will do the right thing as long as the value
is fully sign extended.

Cheers,
Ben.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help