linux-kernel - Re: [PATCH] x86: fix probe_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: <48AE022F.6030100@goop.org>
Date:	Thu, 21 Aug 2008 17:02:55 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, 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>
Subject: Re: [PATCH] x86: fix probe_nr_irqs for xen

Yinghai Lu wrote:
> like system vectors with smp-ipi etc?
>   

More or less.  Xen currently uses 6 per-cpu event channels, and it maps
each to its own irq.  My plan is to allocate just 6 irqs, map 6 vectors
to them, and bind each event channel to a vector/cpu pair.  If nothing
else, it will make /proc/interrupts somewhat sane again.


>> Also, implementing probe_nr_irqs() in a more generic (rather than
>> io_apic-specific) way.  Using some interface that queries each irq chip
>> for how many irqs it supports, or something.
>>     
>
> hope we can kill nr_irqs/NR_IRQS
>   

When irqs are truely dynamically allocated?

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