On Tuesday 18 February 2014 18:44:20 Will Deacon wrote: > On Tue, Feb 18, 2014 at 06:21:42PM +0000, Jason Gunthorpe wrote: > > On Tue, Feb 18, 2014 at 12:20:43PM +0000, Will Deacon wrote: > > > + > > > + // BUS_ADDRESS(3) CPU_PHYSICAL(2) SIZE(2) > > > + ranges = <0x1000000 0x0 0x00000000 0x0 0x00000000 0x0 0x00010000>, > > ^^^^^^^^^^^^^^ > > > > This probably shouldn't be 0 in the example, nor in your kvm tool > > output. For example purposes any value will do. > > Hmm, so kvmtool actually provides a PC ioport at 0x0, which is handy since > there's an 8250 down there. That means we have: > > 0x0 - 0x6200 : Weird PC stuff > 0x6200 - 0x10000 : PCI IO space > > Should I just change everything to be offset by 0x6200? Do you have a list of the stuff in there? If that is actually port I/O, leaving it in there may be best, but I agree the example should be changed. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
