From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752171AbaAYAZk (ORCPT ); Fri, 24 Jan 2014 19:25:40 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:39556 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751490AbaAYAZi (ORCPT ); Fri, 24 Jan 2014 19:25:38 -0500 Date: Fri, 24 Jan 2014 16:19:36 -0800 From: "Paul E. McKenney" To: Steven Rostedt Cc: Sebastian Andrzej Siewior , LKML , linux-rt-users , Thomas Gleixner , Clark Williams , "Luis Claudio R. Goncalves" , John Kacur , Mike Galbraith , Joakim Hernberg , Joe Korty , Muli Baron Subject: Re: [PATCH RT v2] timer: Raise softirq if there's irq_work Message-ID: <20140125001936.GB9012@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20140124145157.1f30d447@gandalf.local.home> <20140124150933.22d8c20a@gandalf.local.home> <20140124202039.GA32662@linutronix.de> <20140124153542.6a92ef27@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140124153542.6a92ef27@gandalf.local.home> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14012500-8236-0000-0000-00000666BA7E Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 24, 2014 at 03:35:42PM -0500, Steven Rostedt wrote: > On Fri, 24 Jan 2014 21:20:39 +0100 > Sebastian Andrzej Siewior wrote: > > > * Steven Rostedt | 2014-01-24 15:09:33 [-0500]: > > > > >[ Talking with Sebastian on IRC, it seems that doing the irq_work_run() > > > from the interrupt in -rt is a bad thing. Here we simply raise the > > > softirq if there's irq work to do. This too boots on my i7 ] > > > > It is okay in general because most of the users should not run in bare > > interrupt context. The only exception here is the nohz_full_kick_work > > thing. > > I know we discussed this on IRC, but I wanted to publicly state that > the missing irq work callback was the RCU's rsp_wakeup() function. Failing to invoke rsp_wakeup() when it was needed could potentially stop RCU grace periods from happening, so having rsp_wakeup() happen when it is needed is pretty important... But I would guess that you knew that already. ;-) Thanx, Paul