Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp55694ybx; Mon, 4 Nov 2019 15:44:53 -0800 (PST) X-Google-Smtp-Source: APXvYqxJUQfezeR8gRn8XhBq2LIHQ8sqrPhL66fZHB10wLMEL7i4R8BD76tBPMhqEtvMkpHo1BkC X-Received: by 2002:a17:906:751:: with SMTP id z17mr10352080ejb.313.1572911093558; Mon, 04 Nov 2019 15:44:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572911093; cv=none; d=google.com; s=arc-20160816; b=laCfN3dqsH6+4J+MpgeI8vpLJjcMAITAtiPPbHE1XrxxXg8urSJpn4sLv+tCFoET0v Dk+a0HzksJeYCgHiOXw/1dD/lcUPj46PaBuhnewdEBvWJL9XLxm5vI9hdt8R5k6sl7lQ EOHQTIb4R6/T9crgkzg3MzZ8pcICkjAEycFnBAg4PdSbLIH5LMnq77m32pbTnDt2FTYV h/NiJpwC3BfgU2XDfU/+rE7p0FrpXxAp3Sv2q8VMZtifCR5FJH9uyoP7Gvw8T2ofEz+D Xz2XGdzIEPjydPKp8PwzmVOyZWjThuXaCG8NNQgXeE+t3OUlNQbaH4Es1EBvtGvtAZ8/ WTww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=6DIoSrDRWMaU+XOMVi0/toUXVtv09wAa1CFUt+OHK+s=; b=mFequjekhCcfsMsvYBuCsT/c6y2t8lkVSk7Jo4utoXht4QFdKUy58ZpCuLgGN0Jzla p60wXlwwCVa3VPnw2/AmYsb7N78a0cCp1yJO4N3/lV8qhDiLG/MUdw9danF3Eis6syI3 UGLO+qI0nSFMHRLQIMIUdWXgOmU+MSL3dPOkmQ2psA/6Ou++ee0iWIp4HtImoZsQ1MyE NiVSgAGP/0uiBfwSew0Bt8xLTu1sL2hF8MZvph98t/IqwGVUoKFz2R8r7oHh/SLNWxHV 56uZXYuMCuEyh6hG7apEu2FWFzzZElyF09ovm/aRdJeOnJkgnnd7I0o8fzN/bcWTxlFc AxzQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j16si8003116eda.161.2019.11.04.15.44.29; Mon, 04 Nov 2019 15:44:53 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729928AbfKDXni (ORCPT + 99 others); Mon, 4 Nov 2019 18:43:38 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:39143 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729693AbfKDXni (ORCPT ); Mon, 4 Nov 2019 18:43:38 -0500 Received: from p5b06da22.dip0.t-ipconnect.de ([91.6.218.34] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iRm0Q-0001CA-Ex; Tue, 05 Nov 2019 00:43:30 +0100 Date: Tue, 5 Nov 2019 00:43:29 +0100 (CET) From: Thomas Gleixner To: Scott Wood cc: Peter Zijlstra , Frederic Weisbecker , Ingo Molnar , LKML Subject: Re: [PATCH] timers/nohz: Update nohz load even if tick already stopped In-Reply-To: Message-ID: References: <20191028150716.22890-1-frederic@kernel.org> <20191029100506.GJ4114@hirez.programming.kicks-ass.net> <52d963553deda810113accd8d69b6dffdb37144f.camel@redhat.com> <20191030133130.GY4097@hirez.programming.kicks-ass.net> <813ed21938aa47b15f35f8834ffd98ad4dd27771.camel@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 Nov 2019, Thomas Gleixner wrote: > On Fri, 1 Nov 2019, Scott Wood wrote: > > On Wed, 2019-10-30 at 14:31 +0100, Peter Zijlstra wrote: > > > Oh argh! that's a bit radical of the remote tick. The normal tick runs > > > just fine on idle CPUs, so lets mirror that. > > > > > > How's this then? > > .... > > > > > Needs to be tick_nohz_tick_stopped_cpu(cpu) > > > > After fixing that, I get: > > > > [ 7.439068] WARNING: CPU: 20 PID: 7 at /home/root/linux/kernel/sched/core.c:3681 sched_tick_remote+0x132/0x150 > > So I'm going to apply Scotts patch if nobody comes up with a better idea > until tomorrow. As Peter pointed out to me privately we should rather go and analyze the real thing instead of just applying duct tape. /me drops the patch again.