From: William Lee Irwin III <wli@holomorphy.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, zwane@linuxpower.ca, zab@zabbo.net,
manfred@colorfullife.com, macro@ds2.pg.gda.pl,
Martin.Bligh@us.ibm.com, jamesclv@us.ibm.com,
andrew.grover@intel.com
Subject: Re: 48GB NUMA-Q boots, with major IO-APIC hassles
Date: Sat, 18 Jan 2003 18:27:00 -0800 [thread overview]
Message-ID: <20030119022700.GC780@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301182102420.24250-100000@montezuma.mastecende.com>
On Sat, 18 Jan 2003, William Lee Irwin III wrote:
>> +int vector_to_irq[MAX_NUMNODES][FIRST_SYSTEM_VECTOR - FIRST_DEVICE_VECTOR + 1];
On Sat, Jan 18, 2003 at 09:13:36PM -0500, Zwane Mwaikambo wrote:
> This can never work by looking at the I/O interrupt section of your MP
> table you're overwriting interrupt gates. Therefore this has the
> unfortunate effect of invalidating the rest of the patch.
> Consider this; If you have irq 8 on both ioapic0 and ioapic3 who gets the
> vector setup in the IDT?
Neither. The patch pushes the _real_ vector number and translates it to
a software interrupt number with table lookup, which includes the node ID.
Bill
next prev parent reply other threads:[~2003-01-19 2:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:58 48GB NUMA-Q boots, with major IO-APIC hassles William Lee Irwin III
2003-01-15 11:24 ` Anton Blanchard
2003-01-15 11:55 ` William Lee Irwin III
2003-01-15 12:32 ` Anton Blanchard
2003-01-15 13:10 ` William Lee Irwin III
2003-01-15 15:24 ` Martin J. Bligh
2003-01-15 15:34 ` William Lee Irwin III
2003-01-19 1:43 ` William Lee Irwin III
2003-01-19 1:50 ` William Lee Irwin III
2003-01-19 2:13 ` Zwane Mwaikambo
2003-01-19 2:27 ` William Lee Irwin III [this message]
2003-01-19 2:32 ` Zwane Mwaikambo
2003-01-19 2:55 ` William Lee Irwin III
2003-01-19 3:08 ` William Lee Irwin III
2003-03-28 5:08 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 17:32 Protasevich, Natalie
2003-01-15 22:01 ` Martin J. Bligh
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=20030119022700.GC780@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=andrew.grover@intel.com \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=manfred@colorfullife.com \
--cc=zab@zabbo.net \
--cc=zwane@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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