[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120509091212.GA8585@gmail.com>
Date: Wed, 9 May 2012 11:12:12 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Ido Yariv <ido@...ery.com>
Cc: hpa@...or.com, linux-kernel@...r.kernel.org, shai@...lemp.com,
tglx@...utronix.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/platform] vsmp: Fix number of CPUs when vsmp is disabled
* Ido Yariv <ido@...ery.com> wrote:
> Hi Ingo,
>
> On Tue, May 08, 2012 at 02:25:49PM +0200, Ingo Molnar wrote:
> >
> > On !CONFIG_SMP this produces the following build failure:
> >
> > arch/x86/kernel/vsmp_64.c:171:6: error: ‘setup_max_cpus’ undeclared (first use in this function)
> >
> > Do you want to keep vSMP on UP? If not then you could add a
> > 'depends on SMP' to the vSMP Kconfig entry, avoiding the whole
> > UP problem space.
>
> Oops, sorry for that.
>
> vsmp_64.c is built even if CONFIG_X86_VSMP is not set, so even
> if we set this dependency, it will not fix this issue.
Well, then fix the Makefile rule as well. Is there any point to
using vSMP specific glue on UP kernels?
> How about the following CONFIG_SMP check instead?
Looks pretty ugly, because it just increases the config jungle
instead of reducing it.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists