Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933550AbcKGTRC (ORCPT ); Mon, 7 Nov 2016 14:17:02 -0500 Received: from foss.arm.com ([217.140.101.70]:44324 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933216AbcKGTQ6 (ORCPT ); Mon, 7 Nov 2016 14:16:58 -0500 Date: Mon, 7 Nov 2016 19:16:24 +0000 From: Will Deacon To: Rik van Riel Cc: Thomas Gleixner , Chris Metcalf , Gilad Ben Yossef , Steven Rostedt , Ingo Molnar , Peter Zijlstra , Andrew Morton , Tejun Heo , Frederic Weisbecker , "Paul E. McKenney" , Christoph Lameter , Viresh Kumar , Catalin Marinas , Andy Lutomirski , Daniel Lezcano , Francis Giraldeau , Andi Kleen , Arnd Bergmann , linux-kernel@vger.kernel.org Subject: Re: task isolation discussion at Linux Plumbers Message-ID: <20161107191624.GL20591@arm.com> References: <1471382376-5443-1-git-send-email-cmetcalf@mellanox.com> <1605b087-2b3b-77c1-01ac-084e378f5f28@mellanox.com> <1478545933.14601.30.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1478545933.14601.30.camel@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 933 Lines: 30 On Mon, Nov 07, 2016 at 02:12:13PM -0500, Rik van Riel wrote: > On Mon, 2016-11-07 at 19:36 +0100, Thomas Gleixner wrote: > > On Mon, 7 Nov 2016, Thomas Gleixner wrote: > > > > > > > > > > > == Missing oneshot_stopped callbacks == > > > > > > > > I raised the issue that various clock_event_device sources don't > > > > always support oneshot_stopped, which can cause an additional > > > > final interrupt to occur after the timer infrastructure believes > > > > the > > > > interrupt has been stopped.??I have patches to fix this for tile > > > > and > > > > arm64 in my patch series; Thomas volunteered to look at adding > > > > equivalent support for x86. > > > > > > Right. > > > > Untested patch below should fix that. > >? > > That whitespace cleanup looks awesome, but I am not > optimistic about its chances to bring about functional > change. > > What am I overlooking? It hooks up .set_state_oneshot_stopped? Will