From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 48GB NUMA-Q boots, with major IO-APIC hassles
Date: Wed, 15 Jan 2003 07:34:53 -0800 [thread overview]
Message-ID: <20030115153453.GK919@holomorphy.com> (raw)
In-Reply-To: <840980000.1042644279@titus>
At some point in the past, I wrote:
>> (2) MAX_IO_APIC's got clobbered in the subarch cleanups.
>> -- CONFIG_X86_NUMA was removed, use CONFIG_X86_NUMAQ
>> -- this is greppable, folks...
On Wed, Jan 15, 2003 at 07:24:40AM -0800, Martin J. Bligh wrote:
> That wasn't the subarch cleanups that removed it, please be careful
> what you're saying. I plead not guilty to that one.
Eh? You aren't doing all of them. I think we both know who did this
one (with good intentions, even).
At some point in the past, I wrote:
>> (4) PCI bridges get misnumbered children.
>> -- Brew up a PCI hook for giving child buses their bus numbers.
>> -- Basically, fwd port mbligh's fix for 2.4.x more cleanly.
>> -- Okay, not IO-APIC-related, but it annoys me greatly.
>> -- ink is at least trying to steer me in the right direction here.
On Wed, Jan 15, 2003 at 07:24:40AM -0800, Martin J. Bligh wrote:
> Additional PCI-PCI bridges (eg starfire cards) have never been supported
> in non-boot quads. It's not impossible, but don't be suprised if it
> doesn't work.
It should be fine once the bus numbering, io resources, and IO-APIC's
are dealt with. The bus numbering stuff is out there, io resource stuff
is an open question, and IO-APIC stuff looks uglier than sin (as usual).
Basically, a good chunk of rotorooting appears to be necessary to
assign deal with a number of IRQ sources large enough to make
assign_irq_vector() wrap current_vector, possibly something as
invasive as supporting non-unique vectors for irq_desc's.
At some point in the past, I wrote:
>> (5) Booting with notsc panic()'s.
>> -- Remove tsc_disable assignment in the __setup() call.
>> -- I'd be much obliged if the SMP TSC issues were at long
>> -- last conclusively dealt with. Not IO-APIC-related either,
>> -- but also very annoying.
On Wed, Jan 15, 2003 at 07:24:40AM -0800, Martin J. Bligh wrote:
> You don't have PIT support compiled in, and you turned off TSC support,
> leaving yourself with no timer. There's a patch in my tree to force on
> PIT support for NUMA-Q.
Sounds like a conclusive answer to the TSC for me.
Cheers,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2003-01-15 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:58 William Lee Irwin III
2003-01-15 15:24 ` Martin J. Bligh
2003-01-15 15:34 ` William Lee Irwin III [this message]
2003-03-28 5:08 ` 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=20030115153453.GK919@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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