netdev - Re: [RFC PATCH 13/17] x86: allow the irq->vector translation to be determined outside of ioapic

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:	Tue, 31 Mar 2009 20:16:25 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Gregory Haskins <ghaskins@...ell.com>
Cc:	linux-kernel@...r.kernel.org, agraf@...e.de, pmullaney@...ell.com,
	pmorreale@...ell.com, anthony@...emonkey.ws, rusty@...tcorp.com.au,
	netdev@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC PATCH 13/17] x86: allow the irq->vector translation to be
 determined outside of ioapic

On Tue, 31 Mar 2009 14:43:55 -0400
Gregory Haskins <ghaskins@...ell.com> wrote:

> The ioapic code currently privately manages the mapping between irq
> and vector.  This results in some layering violations as the support
> for certain MSI operations need this info.  As a result, the MSI
> code itself was moved to the ioapic module.  This is not really
> optimal.

This appears to have been muddled in with the vnet patches ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html