mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Jike Song" <albcamus@gmail.com>,
	"Rijndael Cosque" <rijcos@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: What's the status of x2APIC support in Linux kernel?
Date: Sat, 2 Feb 2008 09:43:14 -0800	[thread overview]
Message-ID: <86802c440802020943t7f32133ew24ae946efd7474f5@mail.gmail.com> (raw)
In-Reply-To: <20080202044318.GC12644@one.firstfloor.org>

On Feb 1, 2008 8:43 PM, Andi Kleen <andi@firstfloor.org> wrote:
> > Section 5 and section 9.5 describe 'I/OxAPIC'. I'm not sure if it is
> > already supported by Linux, I guess it is not.
>
> I'm not sure what the point of your questions is.  Do you want to
> do something concrete or are you just interested in random buzzwords?
>
> Anyways as far as I know Linux supports the IO APICs implemented in all
> x86 chipsets fully. That is it doesn't use every possible feature they have,
> but I'm not aware of any particular limitation caused by Linux
> not supporting some IO APIC feature.
>
> The reason for the local x/APIC was that the original non x APIC did not support
> more than 8 logical CPUs being active in the system. Presumably IO xAPIC
> refers to the IO APIC without this limitation too.

APIC: 4bit
xAPIC: 8bit?
x2APIC: 32bit? 4g logical cpu?

patch from SGI for 4096cpu/512node will use apicid as 16 bits, but
actually still use only from 8 bit.
they may wait from Intel release code for x2APIC support for extend
that to 16 bit.
x2APIC will use MSR instead of MMIO to access. that is good.
we don't need to go over mptable or ACPI madt to find phyaddress for local apic.

current code could work well with 8bit local APIC, and 4 bit IOAPIC.
I tried with lifting local apic id to 0x80 or 0x40 above, and io apic
for 0 in linuxbios then load kernel 2.6.21 ( one year ago). it worked
well

YH

  reply	other threads:[~2008-02-02 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  8:43 Rijndael Cosque
2008-02-01  8:53 ` Jike Song
2008-02-01 12:17   ` Andi Kleen
2008-02-01 18:08     ` Siddha, Suresh B
2008-02-14 19:06       ` Bjorn Helgaas
2008-02-14 21:48         ` Siddha, Suresh B
2008-02-02  2:55     ` Jike Song
2008-02-02  4:43       ` Andi Kleen
2008-02-02 17:43         ` Yinghai Lu [this message]
2008-02-01  9:46 ` Peter Zijlstra

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=86802c440802020943t7f32133ew24ae946efd7474f5@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=albcamus@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rijcos@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

all inboxes | Powered by JetHome®