linux-kernel - Re: Xen and incorporating event channels in to 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] [day] [month] [year] [list]

Message-ID: <1297873644.16356.286.camel@zakaz.uk.xensource.com>
Date:	Wed, 16 Feb 2011 16:27:24 +0000
From:	Ian Campbell <Ian.Campbell@...citrix.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	xen-devel <xen-devel@...ts.xensource.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"Ingo Molnar" <mingo@...e.hu>
Subject: Re: Xen and incorporating event channels in to nr_irqs

On Wed, 2011-02-16 at 16:25 +0000, Thomas Gleixner wrote:
> On Wed, 16 Feb 2011, Ian Campbell wrote:
> > On a vaguely related note, what is the future of non-sparse IRQs (on x86
> > and/or generally)?
> 
> In general I want to switch everything over to SPARSE_IRQ. When the
> open coded access to irq_desc[] is gone, which should be mostly the
> case in .39 then switching everything over should be a smooth
> thing. For those archs which do not want to adjust the numbers
> dynamically we simple allocate NR_IRQS in early_irq_init(). So they
> wont even notice.

Sweet, I won't worry myself unduly over the non-SPARSE_IRQ case then.

Thanks,
Ian.


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