On Tue, 31 Mar 2009 14:43:55 -0400 Gregory Haskins <[email protected]> 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 kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
