public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@openbios.org>
To: Andi Kleen <ak@suse.de>
Cc: yhlu <yinghailu@gmail.com>,
	discuss@x86-64.org, linuxbios@openbios.org,
	linux-kernel@vger.kernel.org, yhlu <yhlu.kernel@gmail.com>
Subject: Re: [LinuxBIOS] x86_64: apic id lift patch
Date: Wed, 23 Nov 2005 19:17:08 +0100	[thread overview]
Message-ID: <20051123181708.GB27398@openbios.org> (raw)
In-Reply-To: <20051123173636.GL20775@brahms.suse.de>

* Andi Kleen <ak@suse.de> [051123 18:36]:
> You probably don't need most of it. Just a basic SRAT table (no AML methods)
> and enough to keep the ACPI interpreter from aborting early.
> 
> Or alternatively just fix the bug that caused you to go with discontig
> APICs in the first place.
 
Andi,

I really like your insisting way, but what we tried to express is that
there is hardware that just forces you to have discontiguous APIC ids,
so either you disable parts of the hardware or you are forced to do
nasty things.

Wrt the ACPI tables a good rule of thumb is that if you start to have
some of them you have to have them all. For example if you have a logical
subset of them and try to cover the rest with PIRQ or MPTABLE you will
fail because Linux moans about incorrect tables without even looking at
them. And no, there is no reason for not reading a HPET table when
there's no MADT available. And no, I'm not going to send a fix since I'm
really not motivated to dig into that code any minute more than
absolutely necessary.

I agree that there's a reason that the Linux ACPI code is as it is, but 
in fact as it is a reaction to zillions of buggy bioses it is not always
the best solution to have clean firmware not working with it "fixed" to
behave like the others out there. 

Stefan



  parent reply	other threads:[~2005-11-23 18:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 21:49 x86_64: apic id lift patch yhlu
2005-11-21 22:06 ` Andi Kleen
2005-11-21 22:17   ` yhlu
2005-11-21 22:24     ` Andi Kleen
2005-11-21 22:31       ` yhlu
2005-11-22  9:44         ` Andi Kleen
2005-11-23 16:58   ` [LinuxBIOS] " Ronald G Minnich
2005-11-23 17:35     ` Andi Kleen
     [not found]       ` <2ea3fae10511230943y5f697eb8sdbf891497fa8b88f@mail.gmail.com>
2005-11-23 17:50         ` Andi Kleen
2005-11-23 18:01           ` yhlu
2005-11-23 20:29             ` [discuss] " Andi Kleen
2005-11-23 20:29               ` Ronald G Minnich
2005-11-23 18:28       ` Stefan Reinauer
2005-11-23 20:26       ` Ronald G Minnich
     [not found]     ` <2ea3fae10511230919l4d9829d8j3ce5d820b74074d1@mail.gmail.com>
2005-11-23 17:36       ` Andi Kleen
2005-11-23 17:40         ` yhlu
2005-11-23 18:18           ` Stefan Reinauer
2005-11-23 18:22             ` yhlu
2005-11-23 18:35               ` yhlu
2005-11-23 20:28                 ` [discuss] " Andi Kleen
2005-11-23 18:17         ` Stefan Reinauer [this message]
2005-11-23 20:23       ` Ronald G Minnich
2005-11-23 20:34         ` [discuss] " 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=20051123181708.GB27398@openbios.org \
    --to=stepan@openbios.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxbios@openbios.org \
    --cc=yhlu.kernel@gmail.com \
    --cc=yinghailu@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