mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Len Brown" <lenb@kernel.org>
Cc: "Andrew Morton" <akpm@osdl.org>, "Andi Kleen" <ak@muc.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
Date: Sun, 26 Nov 2006 23:37:47 -0800	[thread overview]
Message-ID: <86802c440611262337o76e5a90cye42602f6295d74a1@mail.gmail.com> (raw)
In-Reply-To: <200611270037.53964.len.brown@intel.com>

On 11/26/06, Len Brown <len.brown@intel.com> wrote:
>
> So the bigger question is why you need these workarounds in the first place.

in the LinuxBIOS, acpi support is there including acpi tables and dsdt
for amd chipset.
but for other chipset, I can not put dsdt there. becase we need one
clean room implementation for dsdt with those chipset.

So I have all acpi tables (SRAT, SLIT, ...) but no dsdt.
We need to use mptable instead of MADT + dsdt for io apic irq routing.

I forget to remove MADT in one test, the kernel will skip the mptable.

After look at the kernel acpi code, it turns out that
acpi_process_madt will set acpi_lapic, and acpi_ioapic.  So
get_smp_config will skip the mptable.

With normal BIOS, if there is problem with DSDT, and you are trying
acpi=noirq, it means you are going to PIC mode instead of APIC mode if
you are skipping mptable.

YH

  reply	other threads:[~2006-11-27  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 23:24 Yinghai Lu
2006-11-27  0:23 ` Andi Kleen
2006-11-27  5:37 ` Len Brown
2006-11-27  7:37   ` Yinghai Lu [this message]
2006-11-28  5:09   ` Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86802c440611262337o76e5a90cye42602f6295d74a1@mail.gmail.com \
    --to=yinghai.lu@amd.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®