linux-kernel - Re: [PATCH] x86: make NR_IRQS on 32bit is same to 64bit

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] [day] [month] [year] [list]

Message-Id: <1226010969.3023.29.camel@calx>
Date:	Thu, 06 Nov 2008 16:36:09 -0600
From:	Matt Mackall <mpm@...enic.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ben Hutchings <bhutchings@...arflare.com>
Subject: Re: [PATCH] x86: make NR_IRQS on 32bit is same to 64bit

On Thu, 2008-11-06 at 23:23 +0100, Ingo Molnar wrote:
> * Matt Mackall <mpm@...enic.com> wrote:
> 
> > On Wed, 2008-11-05 at 22:52 -0800, H. Peter Anvin wrote:
> > > Yinghai Lu wrote:
> > > >>
> > > >> Clean-up sidenote: i think we can now remove the VISWS #ifdef portion
> > > >> for good? Mind sending a patch for that too?
> > > > 
> > > > could remove CONFIG_PARAVIRT too.. Jeremy?
> > > > 
> > > 
> > > This seems like a bad idea, especially for the embedded guys.
> > 
> > I'd actually really like to see us move to dynamically-allocated irq 
> > tables as they're currently huge. But I haven't dug into it deeply 
> > enough to see what sort of gotchas are involved.
> 
> sparseirq (== dynamic IRQ tables) is all implemented already, and most 
> of the details except the final feature-enabler are upstream already.

Thanks for the pointer, I'd missed this going by.

-- 
Mathematics is the supreme nostalgia of our time.

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