public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
	akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
	clameter@sgi.com
Subject: Re: [patch 32/59] x86_64: get boot_cpu_id as early for k8_scan_nodes
Date: Mon, 13 Aug 2007 10:47:27 +0200	[thread overview]
Message-ID: <200708131047.27595.ak@suse.de> (raw)
In-Reply-To: <86802c440708122240l4bd7ea69yc477aec2273755c4@mail.gmail.com>

On Monday 13 August 2007 07:40, Yinghai Lu wrote:

> maybe for intel x86_64, it is hard to make kernel with numa enabled
> with acpi=off.

You would need to write an k8topology.c equivalent for that
hardware. But fortunately it's not needed because they
don't have any ACPI less bios.

> but for amd k8 based system (even for later ...), it is rather simple
> and clear

Sorry I disagree. Most of your APIC patches are neither simple nor clear
and they're all quite risky and likely to break other systems.

The big problem with k8topology.c is that it cannot do its work
on its own,  but needs it to do partly doing CPU setup too. That 
means it cannot just set up state once, but keeps state continually
changing. That makes it quite messy. 

> also we can use that as good debug feature... it is good to verify
> system/hw/bios could work with kernel (acpi=off). So other os without
> acpi support or with broken acpi support still can work...

Debug features are ok if they're simple and don't impact the code
much, but that's not the case here.
Also more and more systems don't work without ACPI for other
reasons so it's not very useful. Also typically modern hardware
doesn't have a mptable so you couldn't use more than one CPU.

-Andi (who sometimes feels LinuxBIOS is more a AntiLinuxBIOS if it
requires such hacks) 

      reply	other threads:[~2007-08-13  8:49 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
2007-08-13  5:40     ` Yinghai Lu
2007-08-13  8:47       ` Andi Kleen [this message]

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=200708131047.27595.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