From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753300AbdFPMAq (ORCPT ); Fri, 16 Jun 2017 08:00:46 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:54273 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753149AbdFPMAo (ORCPT ); Fri, 16 Jun 2017 08:00:44 -0400 Date: Fri, 16 Jun 2017 14:00:28 +0200 (CEST) From: Thomas Gleixner To: Christoph Hellwig cc: Jens Axboe , Keith Busch , linux-nvme@lists.infradead.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/8] genirq/affinity: factor out a irq_affinity_set helper In-Reply-To: Message-ID: References: <20170603140403.27379-1-hch@lst.de> <20170603140403.27379-4-hch@lst.de> 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 Fri, 16 Jun 2017, Thomas Gleixner wrote: > On Sat, 3 Jun 2017, Christoph Hellwig wrote: > > +bool irq_affinity_set(int irq, struct irq_desc *desc, const cpumask_t *mask) > > +{ > > + struct irq_data *data = irq_desc_get_irq_data(desc); > > + struct irq_chip *chip = irq_data_get_irq_chip(data); > > + bool ret = false; > > + > > + if (!irq_can_move_pcntxt(data) && chip->irq_mask) > > + chip->irq_mask(data); > > + > > + if (chip->irq_set_affinity) { > > + if (chip->irq_set_affinity(data, mask, true) == -ENOSPC) > > + pr_crit("IRQ %d set affinity failed because there are no available vectors. The device assigned to this IRQ is unstable.\n", irq); > > + ret = true; > > + } > > + > > + /* > > + * We unmask if the irq was not marked masked by the core code. > > + * That respects the lazy irq disable behaviour. > > + */ > > + if (!irq_can_move_pcntxt(data) && > > + !irqd_irq_masked(data) && chip->irq_unmask) > > + chip->irq_unmask(data); > > There is another issue with this. Nothing updates the affinity mask in > irq_desc, when we just invoke the chip callback. Let me have a look. Indeed. So that magic you do in the next patches (the hotplug callbacks) only work proper for affinity masks with a single cpu set. The problem is that we don't have a distinction between the 'possible' (e.g. set by /proc/irq/affinity) and the effective affinity mask. Needs more thought. Thanks, tglx