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]

Date:	Mon, 07 Jan 2008 10:07:55 -0500
From:	Mark Lord <lkml@....ca>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Venki Pallipadi <venkatesh.pallipadi@...el.com>,
	abelay@...ell.com, lenb@...nel.org, 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

Arjan van de Ven wrote:
..
> if we take a step back; Mark afaics only wants to put 1 in there...
> And that makes sense; either you want the "no latency" C1, or you want the lot
> (esp given that C2 and deeper are at the whim of the bios, what they mean varies
> over time. Actually even C1 does that on some AMD systems);
> 
> Longer term I'd suggest we make an option that basically is "C1 only",
> (or technically, "use hlt only")
> that solves Marks VMWARE thing, and is a lot closer to what people really want.
..

Yeah, that makes sense.

> Well, that and if VMWARE really can't deal with latency in their kernel module
> they should use the proper code for that. It's also a ton easier to implement, since
> it basically is "don't use the CPUIDLE idle loop, but use the traditional hlt one"
..

I don't think it's so much VMware itself, as it is the guest OS inside it.

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/