linux-kernel - Re: [PATCH] x86: make 32bit MAX_HARDIRQSS_PER_CPU to be NR

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]

Message-ID: <20090114111755.GN2913@elte.hu>
Date:	Wed, 14 Jan 2009 12:17:55 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: make 32bit MAX_HARDIRQSS_PER_CPU to be NR_VECTORS


* Yinghai Lu <yinghai@...nel.org> wrote:

> Impact: clean up to be same as 64bit
> 
> 32bit is use per-cpu vector too, so don't use default NR_IRQS
> 
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> 
> ---
>  arch/x86/include/asm/hardirq_32.h  |    3 +++
>  arch/x86/include/asm/irq_vectors.h |    4 ++--
>  2 files changed, 5 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6/arch/x86/include/asm/hardirq_32.h
> ===================================================================
> --- linux-2.6.orig/arch/x86/include/asm/hardirq_32.h
> +++ linux-2.6/arch/x86/include/asm/hardirq_32.h
> @@ -20,6 +20,9 @@ typedef struct {
>  
>  DECLARE_PER_CPU(irq_cpustat_t, irq_stat);
>  
> +/* We can have at most NR_VECTORS irqs routed to a cpu at a time */
> +#define MAX_HARDIRQS_PER_CPU NR_VECTORS
> +
>  #define __ARCH_IRQ_STAT
>  #define __IRQ_STAT(cpu, member) (per_cpu(irq_stat, cpu).member)

applied to tip/x86/cleanups. Btw., isnt the irq_vectors.h bit (mentioned 
in the diffstat) missing?

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