From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Tejun Heo <htejun@gmail.com>, Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage
Date: Tue, 27 Jan 2009 15:31:42 +0000 [thread overview]
Message-ID: <1233070302.3231.34.camel@localhost.localdomain> (raw)
In-Reply-To: <20090127113734.GA28249@elte.hu>
On Tue, 2009-01-27 at 12:37 +0100, Ingo Molnar wrote:
> * Tejun Heo <htejun@gmail.com> wrote:
>
> > From: James Bottomley <James.Bottomley@HansenPartnership.com>
> >
> > Impact: build fix
> >
> > x86_cpu_to_apicid and x86_bios_cpu_apicid aren't defined for voyage.
> > Earlier patch forgot to conditionalize early percpu clearing. Fix it.
>
> > +#ifdef CONFIG_X86_LOCAL_APIC
> > early_per_cpu_ptr(x86_cpu_to_apicid) = NULL;
> > early_per_cpu_ptr(x86_bios_cpu_apicid) = NULL;
> > +#endif
>
> That patch is not acceptable - it is ugly and it adds another set of
> #ifdefs to an already complex piece of code.
>
> As i explained it to James in recent threads, the clean and acceptable
> solution to this class of problems is to switch Voyager away from that
> fragile subarch code to proper generic x86 code. (just like we did it for
> other subarchitectures)
>
> There is nothing in Voyager that justifies special treatment in the area
> of x86 percpu code.
>
> This is one of the mails that explains the principles:
>
> http://lkml.indiana.edu/hypermail/linux/kernel/0901.2/00954.html
>
> Or - if there's no time/interest in doing that, we can mark Voyager as
> CONFIG_BROKEN.
Have you quite finished?
The problem isn't actually voyager specific ... the compile breaks if
you build UP with no local APIC ... for the same reason (you have apic
dependent variables in generic code). Whether voyager is converted to
your quirk infrastructure is irrelevant ... doubly so since the failure
can be produced with UP PC x86 which is already converted.
That file is already a forest of #ifdefs:
jejb@hobholes> grep \\#if setup_percpu.c
#ifdef CONFIG_DEBUG_PER_CPU_MAPS
#ifdef CONFIG_X86_64
#ifdef CONFIG_X86_32
#ifndef CONFIG_NEED_MULTIPLE_NODES
#ifdef CONFIG_X86_LOCAL_APIC
#ifdef CONFIG_X86_64
#ifdef CONFIG_NUMA
#if defined(CONFIG_X86_64) && defined(CONFIG_NUMA)
it can't but be otherwise because it's a monolithic initialisation of a
set of variables defined in conditionally compiled files.
James
next prev parent reply other threads:[~2009-01-27 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090126103243.GA31307@elte.hu>
2009-01-26 13:44 ` [PATCH] x86-32: Fix __per_cpu_load relocation Brian Gerst
2009-01-26 14:18 ` Ingo Molnar
2009-01-27 2:02 ` Tejun Heo
2009-01-27 4:03 ` Tejun Heo
2009-01-27 5:03 ` James Bottomley
2009-01-27 5:29 ` [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage Tejun Heo
2009-01-27 5:29 ` [PATCH 2/2 #tj-percpu] x86: clean up indentation in setup_per_cpu_areas() Tejun Heo
2009-01-27 11:37 ` [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage Ingo Molnar
2009-01-27 11:47 ` Tejun Heo
2009-01-27 12:50 ` Brian Gerst
2009-01-27 13:11 ` Ingo Molnar
2009-01-27 13:21 ` Ingo Molnar
2009-01-27 15:33 ` James Bottomley
2009-01-27 15:31 ` James Bottomley [this message]
2009-01-27 15:50 ` Ingo Molnar
2009-01-27 16:04 ` James Bottomley
2009-01-27 16:25 ` Brian Gerst
2009-01-27 16:53 ` James Bottomley
2009-01-27 10:52 ` [PATCH] x86-32: Fix __per_cpu_load relocation Ingo Molnar
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=1233070302.3231.34.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=brgerst@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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