public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
	yhlu.kernel@gmail.com, clameter@sgi.com
Subject: Re: [patch 32/59] x86_64: get boot_cpu_id as early for k8_scan_nodes
Date: Sun, 12 Aug 2007 12:16:35 +0200	[thread overview]
Message-ID: <200708121216.36110.ak@suse.de> (raw)
In-Reply-To: <200708112242.04946.lenb@kernel.org>

On Sunday 12 August 2007 04:42, Len Brown wrote:
> I hate to burst this bubble,
> but we have evidence that the only reliable way to enumerate
> processors on an ACPI systems is to parse the DSDT.

Yes I agree MADT parsing is in this case significantly simpler
and likely safer and the MADT has to be already correct anyways.

The later fixing up of tables in CPU detect was always not very reliable
and constant maintenance issue.

>
> No, this has nothing to do with the actual ACPI specification,
> but "common industry practice".  ie. what the BIOS vendors are
> shipping that works with Windows but confuses Linux.
>
> This means that all the "parse the MADT early" stuff
> is basically a waste of effort in the long term
> where we will have to change when Linux enumerates
> (and thus enables) the processors in the boot sequence.

I think it's because LinuxBIOS which Y.H. is working on is unable/unwilling
to supply any ACPI tables. So he prefers to kludge around it in the kernel
to adapt to the ever changing hardware.

I already had this argument recently about k8topology.c. It's getting
messier and messier and I would really like to retire it (it was originally
only written for a very early BIOS without SRAT); the only
reason not to is LinuxBIOS.

Apparently one problem is that the Linux ACPI code is not very 
friendly to partial tables (e.g. only SRAT); perhaps that is something
that could be improved.

I skipped these hacks for now because I'm quite sceptical of them.

-Andi

  parent reply	other threads:[~2007-08-12 10:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200708102200.l7AM019i011880@imap1.linux-foundation.org>
2007-08-12  2:42 ` [patch 32/59] x86_64: get boot_cpu_id as early for k8_scan_nodes Len Brown
2007-08-12  4:05   ` Yinghai Lu
2007-08-12 10:16   ` Andi Kleen [this message]
2007-08-13  5:40     ` Yinghai Lu
2007-08-13  8:47       ` Andi Kleen

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=200708121216.36110.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /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