> > BTW, one confusing point here is serial_input_init() which > > hard coded a vector (0x30), which happens to conflict with > > eth0 vector on my tiger box. What's the purpose of this > > registration? Actually the registration here is bogus which > > never severs the purpose. Before my patch, previous logic > > simply injects that vector (0x30) into guest since it's not > > timer/ipi. Even xen wants to handle this vector, the > > hw_interrupt_type assocated with this vector is no_irq_type > > which is also bogus. Since it doesn't work as the code wants, > > I simply disabled the serial_input_init to avoid unnecessary > > warnings like " Unexpected irq vector 0x30 on cpu 0". > > Never understood its purpose! > > Tristan.
Hardcoding 0x30 for keyboard input is very old code that goes back to vBlades. It's possible that it is necessary for running Xen on ski... I'm not sure. Dan _______________________________________________ Xen-ia64-devel mailing list [email protected] http://lists.xensource.com/xen-ia64-devel
