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: Thu, 15 Dec 2011 12:25:06 -0800 [thread overview]
Message-ID: <1323980706.1984.255.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <CAE9FiQXh8tiJ0Aa80uGJBiVv_3-rirMt1roQwZ3dBws-p0=j9A@mail.gmail.com>
On Thu, 2011-12-15 at 11:16 -0800, Yinghai Lu wrote:
> On Wed, Dec 14, 2011 at 11:19 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> >
> >> On Wed, Dec 14, 2011 at 6:24 PM, Nikunj A Dadhania
> >> <nikunj@linux.vnet.ibm.com> wrote:
> >> >>
> >> >> BIOS pre-enabled x2apic, and kernel config does not have x2apic enabled?
> >> > make oldconfig somehow skipped this!! I can see my previous kernel config
> >> > having this enabled.
> >>
> >> looks like recent dmar table related DMAR changing cause that.
> >
> > Which one would that be? Perhaps:
> >
> > iommu: Rename the DMAR and INTR_REMAP config options
> >
> > ? They then need to be fixed if it can be done sanely.
>
> yes.
Not quite sure if I understand the reported issue.
If the old config file had CONFIG_X86_X2APIC and CONFIG_INTR_REMAP set,
doing "make oldconfig" on the newer kernel is asking if I want the new
CONFIG_IRQ_REMAP option to be set and if I say yes, then I have both
CONFIG_X86_X2APIC and CONFIG_IRQ_REMAP set and all is well.
But if I say no, then as expected CONFIG_X86_X2APIC gets disabled (as
IRQ_REMAP is not selected).
> @@ -287,7 +287,7 @@ config SMP
>
> config X86_X2APIC
> bool "Support x2apic"
> - depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
> + depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
> ---help---
> This enables x2apic support on CPUs that have this feature.
>
>
> renaming INTR_REMAP IRQ_REMAP cause that.
>
> Attached patch should fix the problem.
>
While I am ok with the proposed patch (we are going back to the original
behavior which minimizes the number of options that the user need to
select), I am not sure if I understand the problem.
FWIW, Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
next prev parent reply other threads:[~2011-12-15 20:20 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 [this message]
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
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=1323980706.1984.255.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®