From: Nick Piggin <npiggin@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
steiner@sgi.com
Subject: Re: [patch] x86: make UV support configurable
Date: Wed, 21 Jan 2009 03:50:24 +0100 [thread overview]
Message-ID: <20090121025024.GF24891@wotan.suse.de> (raw)
In-Reply-To: <20090120155000.GA27200@elte.hu>
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.)
How's this?
---
drivers/misc/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6/drivers/misc/Kconfig
===================================================================
--- linux-2.6.orig/drivers/misc/Kconfig
+++ linux-2.6/drivers/misc/Kconfig
@@ -170,7 +170,7 @@ config ENCLOSURE_SERVICES
config SGI_XP
tristate "Support communication between SGI SSIs"
depends on NET
- depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_64) && SMP
+ depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP
@@ -197,7 +197,7 @@ config HP_ILO
config SGI_GRU
tristate "SGI GRU driver"
- depends on (X86_64 || IA64_SGI_UV || IA64_GENERIC) && SMP
+ depends on (X86_UV || IA64_SGI_UV || IA64_GENERIC) && SMP
default n
select MMU_NOTIFIER
---help---
prev parent reply other threads:[~2009-01-21 2:50 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
2009-01-21 2:50 ` Nick Piggin [this message]
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=20090121025024.GF24891@wotan.suse.de \
--to=npiggin@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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