linux-kernel - Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account for core busy calculation) sucks rocks

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-next>] [day] [month] [year] [list]

Date:	Wed, 19 Feb 2014 14:47:52 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dirk Brandewie <dirk.j.brandewie@...el.com>
Cc:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Commit fcb6a15c2e7e (intel_pstate: Take core C0 time into account
 for core busy calculation) sucks rocks

Hi Dirk,

I've been having some huge slowdowns on my box building kernels, and I
took the time to bisect it down to commit
fcb6a15c2e7e76d493e6f91ea889ab40e1c643a4 (intel_pstate: Take core C0
time into account for core busy calculation).  With that patch reverted
on Linus's current tree, my build speeds are back up to the normal rate.

The difference is huge, 2 minutes to do a kernel build with that patch
reverted, 8-10 minutes with it applied!  With all of the stable kernel
builds and other trees, this is a huge problem for my workload (all I do
is kernel builds it seems...)

I see some patches you marked as "fixes" that you sent to Rafael, do you
want me to test any of those?  How am I the only one seeing this
problem, do you need my cpu information or anything else?

Oh, and because of the problems, I'll just drop this patch from the
-stable trees for now, I don't want to pollute them with the issue until
it is resolved properly.

thanks,

greg k-h
--
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/