Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities

Andi Kleen wrote:

So if there are any more MSI problems comming up IMHO it should be white list/disabled by default and only turn on after a long time when Windows uses it by default or something. Greg, do you agree?

We should be optimists, not pessimists.

MSI is useful enough that we should turn it on by default in newer systems.

	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/

---

• Follow-Ups:
  • Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
    • From: Andi Kleen <[email protected]>

• 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]>

• Prev by Date: Re: [patch] do_no_pfn
• Next by Date: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• 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):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]