linux-kernel - Re: [PATCH 6/6] x86-64: Support for multiple MSIs

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:	Sat, 12 Jul 2008 10:30:25 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	grundler@...isc-linux.org, tglx@...utronix.de, jgarzik@...ox.com,
	linux-ide@...r.kernel.org, suresh.b.siddha@...el.com,
	benh@...nel.crashing.org, jbarnes@...tuousgeek.org,
	rdunlap@...otime.net, mtk.manpages@...il.com,
	ebiederm@...ssion.com, Matthew Wilcox <willy@...ux.intel.com>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH 6/6] x86-64: Support for multiple MSIs

On Sat, Jul 12, 2008 at 07:54:44AM +0200, Ingo Molnar wrote:
> hm, please implement this symmetrically on 64-bit and 32-bit as well. 
> That will need more IRQ infrastructure changes but that should be OK as 
> it will reduce the gap between the 32-bit and 64-bit side instead of 
> widening it. A good starting point would be to unify/generalize the IRQ 
> vector allocators. (and that would get most of what you need for 
> multi-vector MSI)

OK, I'll look into unifying them on Monday.  Thanks for the review.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/