From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Cc: akpm@zip.com.au
Subject: Re: setup_ioapic_ids_from_mpc()
Date: Sun, 19 Jan 2003 18:17:48 -0800 [thread overview]
Message-ID: <94060000.1043029068@titus> (raw)
In-Reply-To: <20030120011906.GJ780@holomorphy.com>
> Use NUMA-Q specific MP OEM tables to program the physical APIC ID's of
> the IO-APIC's. This fixes boot-time panic()'s on NUMA-Q's in the stock
> version of setup_ioapic_ids_from_mpc().
I think you can just skip this whole routine altogether on NUMA-Q,
it's all pre-programmed for us by firmware. Much smaller patch ;-)
M.
next prev parent reply other threads:[~2003-01-20 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 13:01 setup_ioapic_ids_from_mpc() William Lee Irwin III
2003-01-19 13:15 ` setup_ioapic_ids_from_mpc() William Lee Irwin III
2003-01-19 13:29 ` setup_ioapic_ids_from_mpc() William Lee Irwin III
2003-01-20 1:19 ` setup_ioapic_ids_from_mpc() William Lee Irwin III
2003-01-20 2:17 ` Martin J. Bligh [this message]
2003-01-20 2:21 ` setup_ioapic_ids_from_mpc() William Lee Irwin III
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=94060000.1043029068@titus \
--to=mbligh@aracnet.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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