From: Jesse Barnes <jbarnes@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Disable CONFIG_SMP for IA64_HP_SIM
Date: Wed, 19 May 2004 13:14:40 +0000 [thread overview]
Message-ID: <200405190914.40803.jbarnes@redhat.com> (raw)
In-Reply-To: <20040519012326.GA27655@cse.unsw.EDU.AU>
On Tuesday, May 18, 2004 11:10 pm, Ian Wienand wrote:
> On Wed, May 19, 2004 at 02:59:13AM +0100, Matthew Wilcox wrote:
> > On Tue, May 18, 2004 at 06:35:12PM -0700, David Mosberger wrote:
> > > CONFIG_SMP probably shouldn't depend on CONFIG_IOSAPIC.
> >
> > I agree -- I think the SGI machines don't have an IOSAPIC.
>
> I don't think it would effect the SGI machines as they have their own
> arch/sn/kernel/irq.c?
I'll try it out now. At one point, we needed iosapic.c since some files
referenced symbols there in unused codepaths. I think that's since been
fixed though.
Jesse
next prev parent reply other threads:[~2004-05-19 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 1:23 Disable CONFIG_SMP for IA64_HP_SIM Ian Wienand
2004-05-19 1:35 ` David Mosberger
2004-05-19 1:59 ` Matthew Wilcox
2004-05-19 3:10 ` Ian Wienand
2004-05-19 13:14 ` Jesse Barnes [this message]
2004-05-19 13:21 ` Jesse Barnes
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=200405190914.40803.jbarnes@redhat.com \
--to=jbarnes@redhat.com \
--cc=linux-ia64@vger.kernel.org \
/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