linux-kernel - Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

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: <200801071412.59964.lenb@kernel.org>
Date:	Mon, 7 Jan 2008 14:12:59 -0500
From:	Len Brown <lenb@...nel.org>
To:	Mark Lord <lkml@....ca>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Venki Pallipadi <venkatesh.pallipadi@...el.com>,
	Arjan van de Ven <arjan@...radead.org>, abelay@...ell.com,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, rjw@...k.pl
Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

1. Why does VMware need max_cstate=1 to load quickly?
   It should not, and the fact that it does means
   that something somewhere is seriously broken.

2. Why does the "max_csate=1" workaround help only
   on the dual-core boxes, while the single-core
   boxes still fail to load quickly?

I'm glad that we deleted run-time access to max_cstate --
it seems to have exposed a real bug that needs fixing
and has gone unreported until now.

Indeed, when the real bug is fixed, I propose that
we again move to delete max_cstate as a run-time API.

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