2008/7/9 Stefano Ceccherini <stefano.ceccherini@xxxxxxxxx>: > > > BTW I plan to change this. APIC controllers exist also on non-smp > > configurations. On Fri, Jul 11, 2008 at 2:54 PM, Michael Lotz <mmlr@xxxxxxxx> wrote: > I thought Dustin was actually working on moving the ACPI table scanning > into a standalone service based on what currently is in the SMP > sources, which makes perfect sense. I put it there only because it was > the sole user of it that the time, but now that can and should be > changed. As for always using APICs I wouldn't see why not to use them, > apart from that there seem to be some problems with some devices. But > those need to be addressed sooner or later anyway I think. Passing HPET > infos from the bootloader through kernel args is fine too I guess. > > Regards > Michael > > Sorry about the silence as of late. I do indeed plan to move the ACPI scanning code into its own unit. I agree that it'd be a good idea to use APIC on uniprocessor systems; the ACPI table won't contain en entry for it if it's not present- that seemingly automatically gets handled with apic_ptr being NULL, i believe.. but as far as I know, only the timer checks that (or needs to? What else besides interrupt routing do we use the APIC for?) What devices are in question? :) - DH