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: <47829AA7.3020304@rtr.ca>
Date:	Mon, 07 Jan 2008 16:33:27 -0500
From:	Mark Lord <lkml@....ca>
To:	Len Brown <lenb@...nel.org>
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

Len Brown wrote:
> 1. Why does VMware need max_cstate=1 to load quickly?
..

Eh?  Nothing to do with "loading" anything,
but rather it's simple responsiveness to guest keyboard
input that we're experiencing trouble with.
The guest OS is probably "broken" in that regard,
but setting max_cstate=1 makes it usable here.

> 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?
..

Eh?  Setting max_cstate=1 helps on both single/dual core
boxes/kernels here.  The alternative (newer) latency thing
(that requires a custom kernel module to change on the fly)
is the thing that had no effect at all on our single-core box,
but did seem to help the dual-core more (not verified completely
on dual-core though).

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