Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755718AbZA0Q0J (ORCPT ); Tue, 27 Jan 2009 11:26:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753301AbZA0QZ6 (ORCPT ); Tue, 27 Jan 2009 11:25:58 -0500 Received: from yw-out-2324.google.com ([74.125.46.28]:64892 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753296AbZA0QZ5 (ORCPT ); Tue, 27 Jan 2009 11:25:57 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xCMupQI62cjpgSiyaZg8oplpAZAPd4S2VJY45NIbPxd4Ijq2E96+Iz5udGBYR6s9Km XHN2gUTKyaqZRzNq2LQZYapYJxaFVoB7lzw5MHPLorJVFczn26BHglXsgSMDw3lb0Yit p8Lh/WvmU7HuNiL2DsSXiiae2n6YyvnR3PiSk= MIME-Version: 1.0 In-Reply-To: <1233072253.3231.47.camel@localhost.localdomain> References: <20090126103243.GA31307@elte.hu> <20090126141832.GA31442@elte.hu> <497E6B34.1020508@kernel.org> <497E8778.9060503@gmail.com> <1233032609.3248.78.camel@localhost.localdomain> <497E9B9D.4010102@gmail.com> <20090127113734.GA28249@elte.hu> <1233070302.3231.34.camel@localhost.localdomain> <20090127155044.GB28209@elte.hu> <1233072253.3231.47.camel@localhost.localdomain> Date: Tue, 27 Jan 2009 11:25:56 -0500 Message-ID: <73c1f2160901270825y5e7f3974m830c399074c2e8f1@mail.gmail.com> Subject: Re: [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage From: Brian Gerst To: James Bottomley Cc: Ingo Molnar , Tejun Heo , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2687 Lines: 64 On Tue, Jan 27, 2009 at 11:04 AM, James Bottomley wrote: > On Tue, 2009-01-27 at 16:50 +0100, Ingo Molnar wrote: >> * James Bottomley wrote: >> >> > On Tue, 2009-01-27 at 12:37 +0100, Ingo Molnar wrote: >> > > * Tejun Heo wrote: >> > > >> > > > From: James Bottomley >> > > > >> > > > 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? >> >> What is that supposed to mean? > > It's a conventional response implying your rant wasn't factually > connected to the actual problem at hand. The justification was actually > in the text you cut ... but boils down to you can reproduce it in a non > voyager configuration, so it's not a voyager specific problem. > > The actual problem, as I see it, is how (or whether) to get rid of the > nine #if/#ifdefs that clutter setup_percpu.c ... none of which is > voyager specific. To be fair, setup_percpu.c isn't built on UP. But we're splitting hairs over just 3 conditional variables. I'm open to ideas, but I'm quite certain that any general solution will have more overhead than the current code. I am looking at a patch to remove the early percpu pointers, so the second set of ifdefs would go away. -- Brian Gerst -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/