Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753303AbdIGBTD (ORCPT ); Wed, 6 Sep 2017 21:19:03 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:21089 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752350AbdIGBTB (ORCPT ); Wed, 6 Sep 2017 21:19:01 -0400 From: Paul Burton To: Thomas Gleixner CC: LKML , jeffy , Brian Norris , Marc Zyngier , , , Subject: Re: [2/2] genirq: Warn when IRQ_NOAUTOEN is used with shared interrupts Date: Wed, 6 Sep 2017 18:18:51 -0700 Message-ID: <1682867.tATABVWsV9@np-p-burton> Organization: Imagination Technologies In-Reply-To: References: <20170531100212.210682135@linutronix.de> <2582391.E0BmZJ6Wil@np-p-burton> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2128041.CPJb4S2Ddh"; micalg=pgp-sha256; protocol="application/pgp-signature" X-Originating-IP: [10.20.78.215] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2148 Lines: 55 --nextPart2128041.CPJb4S2Ddh Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Hi Thomas, On Wednesday, 6 September 2017 07:14:50 PDT Thomas Gleixner wrote: > 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 So actually it turns out that getting this to work involves more than just avoiding your warning. I have some code which is mostly working; I'll clean up & send it as an RFC hopefully tomorrow. Thanks, Paul --nextPart2128041.CPJb4S2Ddh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEELIGR03D5+Fg+69wPgiDZ+mk8HGUFAlmwnnsACgkQgiDZ+mk8 HGXAvQ//c4G55VhS2sFzEhgFCW1ygqbi31DMw03b12rqlhF/J506GeVhKjBJEABo 7vyonvd//62XKVKDSBdJGPyULS5Rf4OQ+2xzbXqFS/myMKLiHsR7qDqDxSq7g8Is pkSdq/ZnvbzPGrN7e0BZq/lOdx3hIkLecZq3Y/H10r7z3fmZZQTZWu7IOztxDOfO ++dGb3yYm9cClJUtnFayAELnx6brrBXqztmlZ+vsicpgiZoCiBCDQKiDsqdsy2ne A6XEgC0lMh5kyM+V6DEFspmdnaKuJ+e46KW5FqN2zJn0ZugoW7WUggBd0Df20nNY 7+X2189rulpUe5aqx26qoTt6G+L91ea8nsBMdOdmzBvxZlgll3Wa5Bja6Qd5QWn5 F8z41fwH1NWeWtSJ5MmETADSIMKKLuPZcvQRx9PyRscde3NIZJlRzlBUFDwb8sCZ MNAFTtr4aqXL38Lq9IA/UKkBV92Fqr9Ey0bb8HwPGG7FqE7+ukdgdJ6Ww14FvD2E 8ZCpAlBWckub44aGuBUppYcOYAim16dY5PlTDjQenUT2rJ3EXeOXMbIyJrWSxy4y Ap5kc3QYUE28cmUfwGOZC/wXIGwlT1HMyiVJl84lhX5keZrv/mTur+0MTnEQUNsI VH19eh8wt+lJc3PNkIKR6qpuqqZBaquZHtLbsDnqfNpap9obOY8= =V2KJ -----END PGP SIGNATURE----- --nextPart2128041.CPJb4S2Ddh--