From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751776AbdATRXh (ORCPT ); Fri, 20 Jan 2017 12:23:37 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:33371 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751217AbdATRXg (ORCPT ); Fri, 20 Jan 2017 12:23:36 -0500 Date: Fri, 20 Jan 2017 18:21:09 +0100 From: Sebastian Andrzej Siewior To: Mike Galbraith Cc: Thomas Gleixner , LKML , linux-rt-users , Steven Rostedt Subject: Re: [patch-rt] softirq: Move ksoftirqd_running() under !CONFIG_PREEMPT_RT_FULL Message-ID: <20170120172109.4mcissz3n65uba5a@linutronix.de> References: <20161223163213.szj43nv7rnelkbty@linutronix.de> <1483172410.9872.2.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1483172410.9872.2.camel@gmx.de> User-Agent: NeoMutt/20161126 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016-12-31 09:20:10 [+0100], Mike Galbraith wrote: > > Otherwise, ktimersoftd may not be awakened when it has work to do. so the problem is that we have two softirq threads and we only check the state of the "normal" one even if we would have also the schedule the second one. The approach looks good, applied. > [ 84.087571] NOHZ: local_softirq_pending 02 > [ 84.087593] NOHZ: local_softirq_pending 02 > [ 84.087598] NOHZ: local_softirq_pending 02 > [ 84.087904] NOHZ: local_softirq_pending 02 > [ 84.088526] NOHZ: local_softirq_pending 02 > [ 84.088899] NOHZ: local_softirq_pending 02 > [ 84.089463] NOHZ: local_softirq_pending 02 > [ 115.013470] NOHZ: local_softirq_pending 02 > [ 115.013601] NOHZ: local_softirq_pending 02 > [ 115.013709] NOHZ: local_softirq_pending 02 > > Signed-off-by: Mike Galbraith Sebastian