linux-kernel - Re: [RFC] x86: merge nmi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 18 May 2008 12:25:42 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Cyrill Gorcunov <gorcunov@...il.com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Tom Spink <tspink@...il.com>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jirislaby@...il.com>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [RFC] x86: merge nmi_32-64 to nmi.c

Cyrill Gorcunov wrote:

> yes, but what to do with absence of __nmi_count on 32bit and die_nmi
> uses different number of args? gcc follows both pathes anyway trying
> to evaluate where I prefer it would not... I mean I've got errors
> on compiling procedue 'cause of different number of args for die_nmi
> used in 32bit mode. That is why I've asked Thomas if it possible to
> add "panic" boot option for 32bit mode and make it familiar with 64bit
> mode and merge them eventually.

Sorry just pointed out why the Kconfig idea doesn't work, nothing more.

If you want to avoid ifdefs then you have to unify the functionality
first. Putting syntactical sugar on ifdefs doesn't make sense.

I haven't kept track of the exact state of the code, but if the per cpu
data macros are finally as efficient as the PDA you could move the
nmi_count to per_cpu in both for once.

-Andi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/