Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932538AbdIFOOz (ORCPT ); Wed, 6 Sep 2017 10:14:55 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:48932 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932242AbdIFOOy (ORCPT ); Wed, 6 Sep 2017 10:14:54 -0400 Date: Wed, 6 Sep 2017 16:14:50 +0200 (CEST) From: Thomas Gleixner To: Paul Burton cc: LKML , jeffy , Brian Norris , Marc Zyngier , dianders@chromium.org, tfiga@chromium.org, james.hogan@imgtec.com Subject: Re: [2/2] genirq: Warn when IRQ_NOAUTOEN is used with shared interrupts In-Reply-To: <2582391.E0BmZJ6Wil@np-p-burton> Message-ID: References: <20170531100212.210682135@linutronix.de> <45610923.Yru6qcift9@np-p-burton> <2582391.E0BmZJ6Wil@np-p-burton> 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 Content-Length: 657 Lines: 17 On Wed, 6 Sep 2017, Paul Burton wrote: > On Wednesday, 6 September 2017 01:16:48 PDT Thomas Gleixner wrote: > > What's the problem with IRQ_NOAUTOEN and do > > > > setup_percpu_irq(); > > enable_percpu_irq(); > > > > on the boot CPU and then later call it when the secondary CPUs come up in > > cpu bringup code or a hotplug state callback? > > There's no problem with that at all, apart from that it triggers your warning > when the boot CPU calls setup_percpu_irq(). Ok, I misread the whole thing somehow. What you are saying is that you need per cpu interrupts which can be shared .... Hrmpf, ok. I'll have a look from that side then