From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <htejun@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.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 14:11:08 +0100 [thread overview]
Message-ID: <20090127131108.GE23121@elte.hu> (raw)
In-Reply-To: <497EF43D.9010303@gmail.com>
* Tejun Heo <htejun@gmail.com> wrote:
> Hello, Ingo.
>
> Ingo Molnar wrote:
> >> +#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.
>
> Well, although the patch itself does add #ifdef, if you look over the
> whole series, voyager is now a much more conforming citizen in the x86
> world. There are several solutions to this particular one.
>
> 1. Just let apic stuff defined and not use it in voyager if the ifdef
> is disturbing. IIUC, apic isn't used in voyager at all, right?
>
> 2. Clean up early percpu stuff so that it each early percpu variable
> doesn't need to be explicitly copied and cleared, which is the
> actual problem here.
>
> 3. But, then again, the current interim and ugly way of doing it isn't
> too bad considering the small number of early per cpu users.
>
> To me the current form doesn't look too bad but if it's too ugly, maybe
> doing #2 is not such a bad idea such that early percpu can be
> transferred to percpu in more systematic way. It still feels a bit like
> overdoing it tho.
>
> What do you think?
This issue might be minor, but it's the death of a thousand cuts. It
should switch to the generic x86 code, use smp_ops to wrap/express its own
SMP weirdnesses [and extend it where needed - because _that_ is a step
forward for the whole code - fixing build bugs isnt] and then such
problems simply wont occur.
Ingo
next prev parent reply other threads:[~2009-01-27 13:11 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 [this message]
2009-01-27 13:21 ` Ingo Molnar
2009-01-27 15:33 ` James Bottomley
2009-01-27 15:31 ` James Bottomley
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=20090127131108.GE23121@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brgerst@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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