Messages in this thread | | | Subject | Re: [Fastboot] [PATCH] i386: move apic init in init_IRQs | From | (Eric W. Biederman) | Date | Tue, 25 Oct 2005 01:17:03 -0600 |
| |
Vivek Goyal <vgoyal@in.ibm.com> writes: > I have attached a patch with the mail which is now using > boot_cpu_physical_apicid to hard set presence of boot cpu instead of > hard_smp_processor_id(). But the interesting questoin remains why BIOS is > not reporting the boot cpu.
Ok. I don't know if we care but I do know why we were not seeing the report from the bios about your boot processor. We record information about cpus for up to NR_CPUS, and since you had a UP kernel NR_CPUS was one.
From your earlier boot log.
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x03] enabled) > Processor #3 6:10 APIC version 17 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > Processor #0 6:10 APIC version 17 > WARNING: NR_CPUS limit of 1 reached. Processor ignored. > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) > Processor #1 6:10 APIC version 17 > WARNING: NR_CPUS limit of 1 reached. Processor ignored. > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) > Processor #2 6:10 APIC version 17 > WARNING: NR_CPUS limit of 1 reached. Processor ignored.
So it looks like we have this problem completely fixed.
I don't see a good way to ensure that we always record our boot apicid when we boot a multiple processor system and only use one processor.
Eric
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |