From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754151AbYERH0I (ORCPT ); Sun, 18 May 2008 03:26:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750954AbYERHZ4 (ORCPT ); Sun, 18 May 2008 03:25:56 -0400 Received: from gw.goop.org ([64.81.55.164]:36620 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751645AbYERHZz (ORCPT ); Sun, 18 May 2008 03:25:55 -0400 Message-ID: <482FD9F2.8080204@goop.org> Date: Sun, 18 May 2008 08:25:38 +0100 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Thomas Gleixner CC: "Maciej W. Rozycki" , Tom Spink , Cyrill Gorcunov , Ingo Molnar , "H. Peter Anvin" , LKML , Jiri Slaby , Sam Ravnborg , Andi Kleen Subject: Re: [RFC] x86: merge nmi_32-64 to nmi.c References: <20080517192200.GA6914@cvg> <7b9198260805171328u555eec17t3597f3378edbda88@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thomas Gleixner wrote: > Definitely, but we should do it at the Kconfig level which allows us > to have integer defines as well, so we end up with something like: > > static inline unsigned int get_nmi_count(int cpu) > { > return CONFIG_X86_64 ? cpu_pda(cpu)->__nmi_count : nmi_count(cpu); > } > Unfortunately that doesn't work because when CONFIG_X86_64 isn't defined it doesn't expand to 0. It would be nice if CONFIG_* expanded to 0/1, but we'd need to change all the #ifdef CONFIG_* to #if CONFIG_*... J