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:	Fri, 22 Aug 2008 06:26:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Alex Nixon <alex.nixon@...rix.com>,
	Alan Mayer <ajm@....com>
Subject: Re: [PATCH] x86: fix probe_nr_irqs for xen


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> > hope we can kill nr_irqs/NR_IRQS
> 
> When irqs are truely dynamically allocated?

they in essence already are truly dynamic in tip/master. Not yet 
unconditionally so on x86, we chose to also have a !SPARSEIRQ build 
model to make sure dense IRQ arrays still work fine as well. (that's far 
easier to test and validate than to keep a farm of cross compilers to 
other arches alive.)

But by all means SPARSEIRQ is the primary and only model on x86.

We could even plug in the dynamic vector allocator from Alan Mayer now, 
both on 32-bit and on 64-bit x86: Yinghai, any complications expected 
there? I guess we need to unify the local APIC code first.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ