Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756331AbcJTH2i (ORCPT ); Thu, 20 Oct 2016 03:28:38 -0400 Received: from mail-qt0-f195.google.com ([209.85.216.195]:35572 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753933AbcJTH2g (ORCPT ); Thu, 20 Oct 2016 03:28:36 -0400 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: References: From: Sedat Dilek Date: Thu, 20 Oct 2016 09:28:35 +0200 Message-ID: Subject: Re: [4.9-rc1] Build-time 2x slower To: =?UTF-8?Q?J=C3=B6rg_Otte?= Cc: Linus Torvalds , "Rafael J. Wysocki" , Michal Marek , Ming Lei , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id u9K7SgYF023293 Content-Length: 1457 Lines: 41 On Wed, Oct 19, 2016 at 6:59 PM, Jörg Otte wrote: > 2016-10-19 17:29 GMT+02:00 Linus Torvalds : >> On Wed, Oct 19, 2016 at 4:07 AM, Jörg Otte wrote: >>> >>> Additional info: I usally use schedutil governor. >>> If I switch to performance governor problems go away. >>> Maybe a cpufreq problem? >> >> Oh, I completely misread the original bug report, and then didn't read >> your confirmation email right. >> >> I thought you had a slower build of the different kernels (when >> building on the same kernel), and that the _build_ itself had slowed >> down for some reason. But you're actually saying that doing the _same_ >> build actually takes longer when running on 4.9-rc1. > > Exactly! > > Btw: ondemand governor is also good. > >> There are a few small cpufreq changes there in between commit >> 29fbff8698fc (that you reported was fine - please tell me I got _that_ >> right, at least?) and 4.9-rc1. > > Perfect! That's what I mean. > >> Adding Rafael to the cc. >> >> That said, none of them look all that likely to me. It *would* be good >> if you could bisect it a bit (perhaps not fully, but a couple of >> bisection steps to narrow down what area it is). > > I try that tomorrow. > I switched over to ***schedutil*** as default-cpufreq-governor with v4.8 in my init-scripts. Didn't try any other cpufreq-governor and had no time to play more with this issue. - Sedat -