From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86: make UV support configurable
Date: Tue, 20 Jan 2009 17:06:37 +0100 [thread overview]
Message-ID: <20090120160637.GB32650@elte.hu> (raw)
In-Reply-To: <20090120155334.GB225848@sgi.com>
* Jack Steiner <steiner@sgi.com> wrote:
> On Tue, Jan 20, 2009 at 04:50:00PM +0100, Ingo Molnar wrote:
> >
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> > > * Nick Piggin <npiggin@suse.de> wrote:
> > >
> > > > Fixed the EFI omission since the last patch. I have not changed the
> > > > Kconfig to include (what I think are) false dependencies (which really
> > > > frustrate me when things get badly tangled up). If people want to test
> > > > as much stuff as possible even that is not supported by their hardware,
> > > > we have allyesconfig/allmodconfig. I don't think UV is particularly
> > > > special in that respect (we allow Intel, AMD, etc CPUs to be configured
> > > > out)
> > > >
> > > > If anything, X86_UV should *select* MAXSMP, rather than the other way
> > > > around. That would be more logical, but even then I don't like adding
> > > > still a false dep because one might have a small UV system, or want to
> > > > test with different NR_CPUS.
> > > >
> > > > Anyway, I think this patch is good as-is. If someone wants to streamline
> > > > config options with subsequent patches, that's great. If Ingo can be
> > > > convinced of a better arrangement, fine.
> > >
> > > Applied to tip/x86/uv, thanks Nick!
> >
> > hm, build failure with the attached config:
> >
> >
> > drivers/built-in.o: In function `gru_cpu_fault_map_id':
> > : undefined reference to `per_cpu____uv_hub_info'
> > drivers/built-in.o: In function `gru_fault':
> > : undefined reference to `per_cpu____uv_hub_info'
> > drivers/built-in.o: In function `gru_try_dropin':
> > grufault.c:(.text+0xbfc6e): undefined reference to
> > `per_cpu____uv_hub_info'
> > grufault.c:(.text+0xc0042): undefined reference to
> > `per_cpu____uv_hub_info'
> > [...]
> >
> > (if possible please send a delta fix on top of your previous patch.)
>
> The GRU driver makes sense only on UV & IA64 configurations.
that's not expressed in the Kconfig rules.
Ingo
next prev parent reply other threads:[~2009-01-20 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 3:36 [patch] x86: make UV support configurable Nick Piggin
2009-01-20 14:27 ` Ingo Molnar
2009-01-20 15:50 ` Ingo Molnar
2009-01-20 15:53 ` Jack Steiner
2009-01-20 16:06 ` Ingo Molnar [this message]
2009-01-21 2:50 ` Nick Piggin
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=20090120160637.GB32650@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=steiner@sgi.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