From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: Latest tip kernel(3.2-rc1-tip_cf6b3899) fails to boot on x3850x5 machine
Date: Fri, 16 Dec 2011 18:18:09 -0800 [thread overview]
Message-ID: <1324088289.1984.305.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <CAE9FiQWzqTGLq2-8Zn4bydCxqA6JL0JVQyDzCtadUCt8nwNWnQ@mail.gmail.com>
On Fri, 2011-12-16 at 10:03 -0800, Yinghai Lu wrote:
> On Fri, Dec 16, 2011 at 12:40 AM, Ingo Molnar <mingo@elte.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
prev parent reply other threads:[~2011-12-17 2:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:48 Nikunj A Dadhania
2011-12-14 13:30 ` Thomas Gleixner
2011-12-14 20:17 ` Thomas Gleixner
2011-12-14 20:35 ` Yinghai Lu
2011-12-14 20:56 ` Thomas Gleixner
2011-12-15 2:24 ` Nikunj A Dadhania
2011-12-15 2:40 ` Yinghai Lu
2011-12-15 7:19 ` Ingo Molnar
2011-12-15 19:16 ` Yinghai Lu
2011-12-15 20:25 ` Suresh Siddha
2011-12-16 3:41 ` Nikunj A Dadhania
2011-12-16 8:36 ` Ingo Molnar
2011-12-17 2:10 ` Suresh Siddha
2011-12-18 8:32 ` Ingo Molnar
2011-12-16 8:40 ` Ingo Molnar
2011-12-16 18:03 ` Yinghai Lu
2011-12-17 2:18 ` Suresh Siddha [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1324088289.1984.305.camel@sbsiddha-desk.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikunj@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®