From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759936AbcISHTU (ORCPT ); Mon, 19 Sep 2016 03:19:20 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:53937 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756367AbcISHTM (ORCPT ); Mon, 19 Sep 2016 03:19:12 -0400 Date: Mon, 19 Sep 2016 09:16:47 +0200 (CEST) From: Thomas Gleixner To: Linus Torvalds cc: LKML , Andrew Morton , Ingo Molnar , "H. Peter Anvin" Subject: Re: [GIT pull] irq fixes for 4.8 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 18 Sep 2016, Linus Torvalds wrote: > On Sun, Sep 18, 2016 at 1:05 AM, Thomas Gleixner wrote: > > > > Boris Brezillon (2): > > genirq: Provide irq_gc_{lock_irqsave,unlock_irqrestore}() helpers > > This seems somewhat questionable. > > The non-irqsafe versions of these functions have specialized non-SMP > versions for them. The new ones don't. > > I pulled it, because I think it's actually the old versions that are > garbage (the locking should become a no-op on UP regardless - except > for the preemption issue which I don't see why it wouldn't be real), > but I think this is inconsistent and should be fixed (or a comment > added about why it is ok). Yes, it lacks a comment. The reason why the non save versions are empty is that these primitives are solely used in the irq chip hotpath functions. UP folks wanted to avoid the preempt disable/enable in these anyway interrupt disabled contexts. Thanks, tglx