On 05/06/2011 12:10 PM, Pekka Enberg wrote: > On Fri, May 6, 2011 at 11:08 AM, Cyrill Gorcunov <gorcunov@xxxxxxxxx> wrote: >> Yes, that is what we do, and it seems to be the "right" way how sane bios >> should behave, same time (i might be wrong since I didn't checked this >> part of kernel sources) the kernel might scan memory for pci configs and >> read pis/irq directly from there, I think this way kernel workaround broken >> bioses but now sure if we should rely on this feature. > > That's not a problem, though, is it? As long as you use the "device > tree" to set up the PCI configs as well, it's irrelevant where the > kernel picks them up, no? Yeah, if we have own "tracking" tool to allocate irqs/pins we put consistent data into both mptable and pci config space. Which of course means we need some more code for allocator/tracker ;) -- Thanks, Cyrill -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
