From: Steffen Persvold <sp@numascale.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
daniel@numascale-asia.com, mingo@elte.hu,
jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH tip] Fix build failure x86_default_fixup_cpu_id() with !CONFIG_SMP
Date: Tue, 06 Dec 2011 12:44:46 +0100 [thread overview]
Message-ID: <4EDE002E.8040007@numascale.com> (raw)
In-Reply-To: <4EDDFE79.9010109@linux.vnet.ibm.com>
On 12/6/2011 12:37, Srivatsa S. Bhat wrote:
> Hi Kamalesh,
>
> On 12/06/2011 04:17 PM, Kamalesh Babulal wrote:
>
>> Hi,
>>
>> tip (a4a7e7e29333) build fails, when compiled with !CONFIG_SMP.
>> I have only build tested the patch.
>>
>> x86: Fix x86_default_fixup_cpu_id() build failure with !CONFIG_SMP
>>
>> arch/x86/kernel/cpu/common.c: In function 'x86_default_fixup_cpu_id':
>> arch/x86/kernel/cpu/common.c:1149: error: 'struct cpuinfo_x86' has no member named 'phys_proc_id'
>> make[3]: *** [arch/x86/kernel/cpu/common.o] Error 1
>>
>> the code was introduced by commit 64be4c1c24. This patch
>> introduced #ifdef to guard !SMP case.
>>
>> Signed-off-by: Kamalesh Babulal<kamalesh@linux.vnet.ibm.com>
>> ----
>
>
> There was a similar build-fix patch by Steffen Persvold at:
> https://lkml.org/lkml/2011/12/6/28
>
> That would solve your case too, right?
>
I would hope so (I tested with !CONFIG_SMP also), albeit I used :
#ifdef CONFIG_NUMA
and not
#ifdef CONFIG_SMP
but I don't think you can compile with CONFIG_NUMA without having
CONFIG_SMP (if I read the Kconfig correctly..).
I used CONFIG_NUMA because the code-path doesn't really make sense on
non-numa nodes.
Cheers,
--
Steffen Persvold, Chief Architect NumaChip
Numascale AS - www.numascale.com
Tel: +47 92 49 25 54 Skype: spersvold
next prev parent reply other threads:[~2011-12-06 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 10:47 [PATCH tip] Fix build failure x86_default_fixup_cpu_id() with !CONFIG_SMP Kamalesh Babulal
2011-12-06 11:37 ` Srivatsa S. Bhat
2011-12-06 11:44 ` Steffen Persvold [this message]
2011-12-06 16:21 ` Kamalesh Babulal
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=4EDE002E.8040007@numascale.com \
--to=sp@numascale.com \
--cc=daniel@numascale-asia.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=srivatsa.bhat@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).