> Actually, Jeremy suggested claiming the entire IO space. That works for > Xen domU too, and makes some amount of sense.
Agreed > > Better yet just don't compile in the old IDE stuff, lguest doesn't have a > > PCI or ISA bus anyway. > > Sure, but the "run the same kernel as guest and host" is a really nice > feature. Modules dear boy, modules ;) > > Alternatively make the IDE I/O space return 0xFF and it'll skip them > > anyway. > > Hmm, every "in" should be returning 0xFFs, but I still get the delay and > the probing. Xen domU gets it too. Can you see in a debugger where it is spending the time. 0xFF should be taken as "no port, move on nothing to see" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
