[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1324088289.1984.305.camel@sbsiddha-desk.sc.intel.com>
Date: Fri, 16 Dec 2011 18:18:09 -0800
From: Suresh Siddha <suresh.b.siddha@...el.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Nikunj A Dadhania <nikunj@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
Joerg Roedel <joerg.roedel@....com>
Subject: Re: Latest tip kernel(3.2-rc1-tip_cf6b3899) fails to boot on
x3850x5 machine
On Fri, 2011-12-16 at 10:03 -0800, Yinghai Lu wrote:
> On Fri, Dec 16, 2011 at 12:40 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> > IRQ_REMAP is a 'complex' option:
> >
> > config IRQ_REMAP
> > bool "Support for Interrupt Remapping (EXPERIMENTAL)"
> > depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
> > select DMAR_TABLE
> >
> > and selecting such complex options is generally dangerous, as
> > the sub-dependencies are not explicitly selected. So if say
> > PCI_MSI or ACPI are disabled, the select will still be performed
> > by X86_X2APIC.
> >
> > Can we make the IRQ_REMAP default depend on X86_X2APIC or so, to
> > solve this problem?
>
> but user could use IRQ_REMAP without x2apic.
Ingo's recommendation is for the default value. We can have multiple
default conditions and the user can always override.
So I am ok with Ingo's suggestion.
> BTW:
> Suresh, can we remove EXPERIMENTAL for IRQ_REMAP now?
Like Google products, beta for a long time ;)
Seriously, we can plan to remove this experimental in the next release.
thanks,
suresh
--
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/
Powered by blists - more mailing lists