From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: Borislav Petkov <bp@alien8.de>, Yinghai Lu <yinghai@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Weidong Han <weidong.han@intel.com>,
David Woodhouse <David.Woodhouse@intel.com>
Subject: Re: [regression] 3.7 ends in APIC panic
Date: Sun, 16 Dec 2012 20:46:06 +0100 [thread overview]
Message-ID: <50CE24FE.3030409@itwm.fraunhofer.de> (raw)
In-Reply-To: <20121216191347.GB14678@liondog.tnic>
On 12/16/2012 08:13 PM, Borislav Petkov wrote:
> On Sun, Dec 16, 2012 at 07:28:59PM +0100, Bernd Schubert wrote:
>> CONFIG_X86_X2APIC depends on CONFIG_IRQ_REMAP, which I disabled as it
>> is marked as experimental...
>
> You shouldn't pay too much attention to CONFIG_EXPERIMENTAL because it
> is on its way out from the kernel tree.
I usually don't too much, if I understand what it is about and what are
the consequences.
>
> But if you don't want to have interrupt remapping on your system,
> you can disable it nevertheless. Wait, you can't: according to
> d0b03bd1c6725a3463290d7f9626e4b583518a5a, you can use x2apic without
> interrupt remapping but interrupt remapping needs to be enabled before
> x2apic.
Hmm, I read it the other way around - x2apic depends on interrupt
remapping, but interrupt remapping can be used without x2apic.
The help text of CONFIG_IRQ_REMAP also says "x2APIC enhancements or to
support platforms with CPU's having > 8 bit APIC ID, say Y." I guess may
CPU has the latter? Can the kernel panic a bit improved to help user to
understand what needs to be enabled?
Thanks,
Bernd
next prev parent reply other threads:[~2012-12-16 19:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:58 Bernd Schubert
2012-12-16 11:35 ` Ingo Molnar
2012-12-16 15:33 ` Bernd Schubert
2012-12-16 17:43 ` Yinghai Lu
2012-12-16 17:45 ` Yinghai Lu
2012-12-16 18:01 ` Bernd Schubert
2012-12-16 18:07 ` Yinghai Lu
2012-12-16 18:28 ` Bernd Schubert
2012-12-16 19:13 ` Borislav Petkov
2012-12-16 19:46 ` Bernd Schubert [this message]
2012-12-16 20:39 ` Borislav Petkov
2012-12-17 9:34 ` Bernd Schubert
2012-12-17 10:00 ` Borislav Petkov
2012-12-17 13:11 ` Bernd Schubert
2012-12-17 9:27 ` Bernd Schubert
2012-12-17 14:02 ` Ingo Molnar
2012-12-17 16:53 ` Yinghai Lu
2012-12-17 16:56 ` H. Peter Anvin
2012-12-17 17:03 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2012-12-13 12:16 Bernd Schubert
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=50CE24FE.3030409@itwm.fraunhofer.de \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=David.Woodhouse@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=weidong.han@intel.com \
--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
Powered by JetHome