linux-kernel - Re: [tip:perf/urgent] perf, x86: Complain louder about BIOSen corrupting CPU/PMU state and continue

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:	Fri, 25 Mar 2011 09:44:24 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	mingo@...hat.com, hpa@...or.com, acme@...hat.com,
	linux-kernel@...r.kernel.org, eric.dumazet@...il.com,
	torvalds@...ux-foundation.org, a.p.zijlstra@...llo.nl,
	efault@....de, fweisbec@...il.com, rostedt@...dmis.org,
	tglx@...utronix.de, mingo@...e.hu
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/urgent] perf, x86: Complain louder about BIOSen
 corrupting CPU/PMU state and continue

On Fri, Mar 25, 2011 at 4:52 AM, tip-bot for Ingo Molnar <mingo@...e.hu> wrote:
>
> perf, x86: Complain louder about BIOSen corrupting CPU/PMU state and continue

I don't think this should go into "urgent". It's more of an annoyance
than anything we need to fix in 39.

Also, don't we need to make sure that the event isn't tied to the SCI
line? I thought the affected BIOSen did something odd with the local
apic setup too? But that might be some fevered nightmare dream of
mine, and/or just a misunderstanding from the hallway discussion I've
had with people about this.

This might also be something we do want to give a kernel command line
option for. As in "bios=allow-annoying-pmu-thing" or whatever.

                    Linus
--
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/