Re: HEADSUP: New i386 interrupt and SMP code..

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 10/31/03

  • Next message: Alp ATICI: "Re: HEADSUP: New i386 interrupt and SMP code.." 
    Date: Fri, 31 Oct 2003 10:21:21 -0500 (EST)
To: arch@FreeBSD.org

    On 31-Oct-2003 David O'Brien wrote:
    > On Thu, Oct 30, 2003 at 05:34:47PM -0500, John Baldwin wrote:
    >> Downsides:
    >> - ACPI will no longer work as a module for know. The reason
    >> for this is that ACPI's APIC enumerator needs to be able
    >> to hook into a SI_SUB_TUNABLES - 1 SYSINIT() due to existing
    >> code that wants to know the available CPUs in the system
    >> very early (specifically, UMA).
    >
    > How will one not have to deal with fscked-up AML BIOS code, when one
    > wants to use MADT rather than mptable's to use the APIC?
    >
    > I.E., the ACPI-AML bits should be seperatable from the ACPI-MADT bits.

    It can't. The MP Table provides PCI interrupt routing information
    in addition to enumerating APICs. Just look at some 'mptable'
    output for comparison. ACPI's PCI interrupt routing information
    is not listed in the MADT, but in _PRT objects in the ACPI namespace.

    You could use the MADT w/o ACPI, but then you would have to use no
    PCI interrupts. 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Alp ATICI: "Re: HEADSUP: New i386 interrupt and SMP code.."

    Relevant Pages

    • [PATCH RFC] x86/acpi: dont ignore I/O APICs just because theres no local APIC
      ... Parse the ACPI MADT for I/O APIC information, even if the cpu has no ... full control over the local APICs, ... the I/O APICs via Xen's event channel mechanism. ...
      (Linux-Kernel)
    • Re: panic: probing for non-PCI bus
      ... ACPI has worked before, and it still ... acpu_cpu is not the same thing as CPUs listed in the MADT. ... then FreeBSD won't find any APICs and won't be ... able to trust ACPI PCI interrupt routing. ...
      (freebsd-current)
    • Re: Problems with AMD64 and 8 GB RAM?
      ... I can't see any reference to anything like an MADT ... Does that mean that there isn't one, or that ACPI can't find ... such), but "APIC" is the 4 character signature of the MADT, hence ... addresses listed here for the APICs aren't ...
      (freebsd-stable)
    • Re: panic: probing for non-PCI bus
      ... > acpu_cpu is not the same thing as CPUs listed in the MADT. ... then FreeBSD won't find any APICs and won't be ... > able to trust ACPI PCI interrupt routing. ...
      (freebsd-current)