Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2614549ybt; Fri, 3 Jul 2020 13:55:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyfYgdQ/+VZBnaE9MTAPZNDlHwqekh9LuAyfR9xwCfDD0gSW1RaouJSCeaRIZTBug3kw40B X-Received: by 2002:a05:6402:134e:: with SMTP id y14mr43121910edw.4.1593809728730; Fri, 03 Jul 2020 13:55:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593809728; cv=none; d=google.com; s=arc-20160816; b=TIQfdNylnhbblSxPmTOkWJjtkXorK1AOEAm1i5P7kh+mTl0oOaxff4DmPOZfsWjtGm 4B7W6Iel6zQDPGMJ7rSmwHQKumalk2THEjTVBx/va1656tQkv1GNEFrNKUhKTnVmEptE GlNqANLXuNb3rdeF+yHtiPVqEBsUaaGpokRNk6eKz2Nb59+BMqNxf/Uh4Ko2KETdlqxI 3Y6DFfQtangmpJl7FV5zXUX8iAQlPl8uWZZv5EdDm1dUKQkC3tZLPa6Vh9y11BgbDOma L9CyZFXDgpjJ1oizm6aTWGWOrsue6sW8TGji0CLWac1EuR2zaHwapdBw1P4PZCFfaH2v 53ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date; bh=sJbNICqslaerh5HtD2SjbXVCNBBvpC8FPNCTWwROc1k=; b=a4f3X1IIfTsd6C2RQFT6SepeI5hgPv7qzJiNzyWyxyDMnASGTCykCjF2LYUn+7amwk eFOLcyW54gZORAm8XNhwCI8pvWJOHsO5ebLt1cGYxgS6nyiRnwe/WSWw6SAmOhIfClIH 4jkoCfjZt1rgvvjOH1R1gV4XPtRj1gm/XFhSmOLrDiQtvYAQcsqxEpuHSTjlZVE+yCYz Q2p+eEVi7MvDjExTjISHsQ29dkZ9g6U3YKW9DpR1DN0Z4xOb6pa0hmObWoVJkdqOegJ9 5U3hzxe7caoexYTibyznoBtDRReohH+IA5Z2dnrRK5Y+H6hXBv28AXZmH5dlgB4CYa+r y9rg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j22si8390533ejv.451.2020.07.03.13.55.05; Fri, 03 Jul 2020 13:55:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726910AbgGCUv7 (ORCPT + 99 others); Fri, 3 Jul 2020 16:51:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726752AbgGCUv7 (ORCPT ); Fri, 3 Jul 2020 16:51:59 -0400 Received: from scorn.kernelslacker.org (scorn.kernelslacker.org [IPv6:2600:3c03:e000:2fb::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2CA93C061794 for ; Fri, 3 Jul 2020 13:51:59 -0700 (PDT) Received: from [2601:196:4600:6634:ae9e:17ff:feb7:72ca] (helo=wopr.kernelslacker.org) by scorn.kernelslacker.org with esmtp (Exim 4.92) (envelope-from ) id 1jrSf4-00057k-B1; Fri, 03 Jul 2020 16:51:54 -0400 Received: by wopr.kernelslacker.org (Postfix, from userid 1026) id F3887560110; Fri, 3 Jul 2020 16:51:53 -0400 (EDT) Date: Fri, 3 Jul 2020 16:51:53 -0400 From: Dave Jones To: Peter Zijlstra Cc: Mel Gorman , Linux Kernel , mingo@kernel.org, Linus Torvalds Subject: Re: weird loadavg on idle machine post 5.7 Message-ID: <20200703205153.GA19901@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Peter Zijlstra , Mel Gorman , Linux Kernel , mingo@kernel.org, Linus Torvalds References: <20200702171548.GA11813@codemonkey.org.uk> <20200702213627.GF3183@techsingularity.net> <20200703090226.GV4800@hirez.programming.kicks-ass.net> <20200703104033.GK117543@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200703104033.GK117543@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Note: SpamAssassin invocation failed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 03, 2020 at 12:40:33PM +0200, Peter Zijlstra wrote: > So ARM/Power/etc.. can speculate the load such that the > task_contributes_to_load() value is from before ->on_rq. > > The compiler might similar re-order things -- although I've not found it > doing so with the few builds I looked at. > > So I think at the very least we should do something like this. But i've > no idea how to reproduce this problem. > > Mel's patch placed it too far down, as the WF_ON_CPU path also relies on > this, and by not resetting p->sched_contributes_to_load it would skew > accounting even worse. looked promising the first few hours, but as soon as it hit four hours of uptime, loadavg spiked and is now pinned to at least 1.00 Dave