linux-kernel - Re: [regression] 3.7 ends in APIC panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 16 Dec 2012 20:13:47 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Bernd Schubert <bernd.schubert@...m.fraunhofer.de>
Cc:	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...nel.org>,
	linux-kernel@...r.kernel.org, Weidong Han <weidong.han@...el.com>,
	David Woodhouse <David.Woodhouse@...el.com>
Subject: Re: [regression] 3.7 ends in APIC panic

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.

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.

Then there was a build breakage which got fixed in
f7d7f866baacc283967ce82ebdfe5d2801059a11 by turning the select IRQ_REMAP
into depends on.

But, this looks to me like the dependency is reversed here: IRQ_REMAP
should depend on X86_X2APIC and not the other way around, right?

Adding some more people to CC.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/