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 14:20:15 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Andi Kleen <andi@...stfloor.org>
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

[Andi Kleen - Sun, May 18, 2008 at 12:15:32PM +0200]
| 
| > 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);
| > }
| 
| #ifdef CONFIG_X86_64 would evaluate true even with CONFIG_X86_64 == 0
| 
| -Andi
|

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.

		- Cyrill -
--
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/