linux-kernel - Re: [PATCH 2/9] x86 idle: remove NOP cpuinfo_x86.hlt_works

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]

Message-ID: <20110331093528.GA19288@elte.hu>
Date:	Thu, 31 Mar 2011 11:35:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Len Brown <lenb@...nel.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	Len Brown <len.brown@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 2/9] x86 idle: remove NOP cpuinfo_x86.hlt_works_ok flag


* Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > Btw., we used to auto-detect broken HLT systems IIRC - but that got lost 
> > already. We should at least honor the boot parameter.
> 
> I don't believe we ever auto detected them or found a way to do so. That
> was why the HLT message was printed before hlt was executed.

Yeah - the CPU hang was unrecoverably deep so no auto-detection was possible.

That's seriously ancient stuff - still, keeping the boot option around (<10 
lines of code) does not hurt anyone.

Thanks,

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