Roland Dreier wrote:
However, the other issue is that CONFIG_PCI_MSI forces some other changes to x86 interrupt handling, even if no devices will ever use MSI. And the changes are such that some systems can't even boot with CONFIG_PCI_MSI enabled. This is the more severe problem, which needs to be handled if you want distros to turn on MSI.
Agreed. We definitely want CONFIG_PCI_MSI-enabled kernels to work in all situations.
Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Dave Olson <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Andi Kleen <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Greg Lindahl <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- From: Roland Dreier <[email protected]>
- Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Prev by Date: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Next by Date: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Previous by thread: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Next by thread: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
- Index(es):
 |