Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp515248imi; Thu, 21 Jul 2022 05:53:33 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tgcDf2DQOth2NG8MaGL5ozhm5X8d7nwJjc30k2ax/JK8gmE8o2oDpMxmA7kXmr9SKG7p5D X-Received: by 2002:a17:902:e5c6:b0:16c:3c8d:3804 with SMTP id u6-20020a170902e5c600b0016c3c8d3804mr42898820plf.30.1658408012748; Thu, 21 Jul 2022 05:53:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658408012; cv=none; d=google.com; s=arc-20160816; b=haNcTNupieYEfMiWuOyGdg5Mw5TUkjazwa959lAgTf4VH2r0SPJYSr3KTQwnlvrFJL +JSPdGNNrzERENBMvWIOXtLqW04xwADzmPu+MAnNLA7rywLZN/ZNsLied4ojkN6/i9rN 2G+XnJu5Al6t6f69DFC2oh+FEFoBYg6qdtdD82bXBcT8QGQM6Nu33mG528T1ba7+mA8+ QywnejMTwgnaRYhXNdjKdTzexaUEhijaTVITg7Pk8t4MUZ+si77ItOs8v+alKKndOa+H m7u7aO9s1zjyPHvUq6pvfsPTtTJYtVgyFcNDpEHEngTgkwVA3NU5xPsen2P163zdWGPH mvjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=9Ssu1IEV13fSbTIGvQByVdGLsBitnFztaBL+6LqkfP8=; b=crmsN5BMqsAy/pFug8X/U4GkKRl5TtIEgiINKsN+dIc5i/bmafptuVtoUin01OYFmZ vrhLV6KpOymMNjhA/U5sFwiQYrXPc6yi86Xfk50knq+/WUrRd60H8kzD3p5MrdueKgTc HM4DUzrmBaAtKOR81muNsiq6GKuYB1Eco3KempeGB3U6lw80qfAV52YsSnwfcXOxbcEz k2JC0eQpcGni5nDzLftiJtmCtPVDxl6x8boKIIqRezi5/f10+NGaiz/B723sExHIMdOY H5XxDTZZ+TUHs7ZZSs35jHbg+KuaeRSewVr8tC2Cm5EFTZMWJ1xL2S4QxmJmUM2qglay PoCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@brainfault-org.20210112.gappssmtp.com header.s=20210112 header.b=nUXp7esk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p37-20020a634f65000000b00419b0c27e02si1983834pgl.729.2022.07.21.05.53.17; Thu, 21 Jul 2022 05:53:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@brainfault-org.20210112.gappssmtp.com header.s=20210112 header.b=nUXp7esk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233541AbiGUM0T (ORCPT + 99 others); Thu, 21 Jul 2022 08:26:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35776 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232164AbiGUM0S (ORCPT ); Thu, 21 Jul 2022 08:26:18 -0400 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ECCF533E20 for ; Thu, 21 Jul 2022 05:26:16 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id d16so2012219wrv.10 for ; Thu, 21 Jul 2022 05:26:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brainfault-org.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9Ssu1IEV13fSbTIGvQByVdGLsBitnFztaBL+6LqkfP8=; b=nUXp7esk4LKpoFZ2B4rzZMsF1LW3V7kxVzkFc47V7AmcaM+dzVvGPno94duetFB85q hV4NO+gygeZYDVvNSoyopjghsXWdyefwFo2uHxtF2I7zARXJACU2wJZCgoQlBuFSaHKq SAloAMBhJAYWXFLmFUQEtlsyel6W7YeAgYOoCQfUlBz8cg3maDoj00nZyM85UwZxfl7o yR9XdZ1Vt2aVBP3E/Mxz9FR3dDD2/XDk3fXkxvnE8KqOPJoWypDH23+ymZMpb63g5Xd9 2IeUKJMEY/7NT7LqkVbKKNq8IwsXZa+bQljytiPslLL3H+lfyCiaZn6RTMBu1x5JL/J1 IFfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9Ssu1IEV13fSbTIGvQByVdGLsBitnFztaBL+6LqkfP8=; b=EYkVKWAsC1KcweqbnbrFll0GxO77UXtrjkCzIrC8SlabARxDcUf7Bkl/pRke80fm+J QjK9uBchKPrQSIljXnh6ZMzXby7dVQKGIxiAxsooMw0xhgdTNMLosOCiwFxS0tQMQJWR glSresPxnR5p0NcyIKpZQpk9K8iEXHZBP2WgeQPpeTEFFLAqPbDgPytLzb4qpk2sZmoj /jKeA+UKCJ6FWcWn+a+lkheTiiGUlwx/x87ndNzoKvcFKmR8vJW0OO2scKFLdDRN5l3Y vKC3/qq8PXwaqxeUarQjpWXh6Ab9sfDZ/EZZAD+em6oOWtJO26CuUSV5KZltkR5DYnp1 GXXA== X-Gm-Message-State: AJIora/iHsA0ql/aywq111r+ad5XVQ1dJG2fzPtsNRLqmpMs7VcqrEJq Ytg2aolqkuEz120bPC8/MUSWfMQF/YV/ieArO4TYrw== X-Received: by 2002:a5d:6c6b:0:b0:1ea:77ea:dde8 with SMTP id r11-20020a5d6c6b000000b001ea77eadde8mr35128041wrz.690.1658406375232; Thu, 21 Jul 2022 05:26:15 -0700 (PDT) MIME-Version: 1.0 References: <20220720152348.2889109-1-apatel@ventanamicro.com> <20220720152348.2889109-4-apatel@ventanamicro.com> <8735euzq60.wl-maz@kernel.org> <5777cae1f73f36316c5e7c09343d8aa7@kernel.org> In-Reply-To: <5777cae1f73f36316c5e7c09343d8aa7@kernel.org> From: Anup Patel Date: Thu, 21 Jul 2022 17:56:02 +0530 Message-ID: Subject: Re: [PATCH v7 3/7] genirq: Add mechanism to multiplex a single HW IPI To: Marc Zyngier Cc: Anup Patel , Palmer Dabbelt , Paul Walmsley , Thomas Gleixner , Daniel Lezcano , Atish Patra , Alistair Francis , linux-riscv , "linux-kernel@vger.kernel.org List" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 21, 2022 at 5:39 PM Marc Zyngier wrote: > > On 2022-07-21 12:44, Anup Patel wrote: > > On Thu, Jul 21, 2022 at 4:30 PM Marc Zyngier wrote: > >> > >> On Wed, 20 Jul 2022 16:23:44 +0100, > >> Anup Patel wrote: > >> > > >> > All RISC-V platforms have a single HW IPI provided by the INTC local > >> > interrupt controller. The HW method to trigger INTC IPI can be through > >> > external irqchip (e.g. RISC-V AIA), through platform specific device > >> > (e.g. SiFive CLINT timer), or through firmware (e.g. SBI IPI call). > >> > > >> > To support multiple IPIs on RISC-V, we add a generic IPI multiplexing > >> > mechanism which help us create multiple virtual IPIs using a single > >> > HW IPI. This generic IPI multiplexing is shared among various RISC-V > >> > irqchip drivers. > >> > > >> > Signed-off-by: Anup Patel > >> > --- > >> > include/linux/irq.h | 16 ++++ > >> > kernel/irq/Kconfig | 4 + > >> > kernel/irq/Makefile | 1 + > >> > kernel/irq/ipi-mux.c | 199 +++++++++++++++++++++++++++++++++++++++++++ > >> > 4 files changed, 220 insertions(+) > >> > create mode 100644 kernel/irq/ipi-mux.c > >> > > >> > diff --git a/include/linux/irq.h b/include/linux/irq.h > >> > index 505308253d23..a97bf13a8965 100644 > >> > --- a/include/linux/irq.h > >> > +++ b/include/linux/irq.h > >> > @@ -1249,6 +1249,22 @@ int __ipi_send_mask(struct irq_desc *desc, const struct cpumask *dest); > >> > int ipi_send_single(unsigned int virq, unsigned int cpu); > >> > int ipi_send_mask(unsigned int virq, const struct cpumask *dest); > >> > > >> > +/** > >> > + * struct ipi_mux_ops - IPI multiplex operations > >> > + * > >> > + * @ipi_mux_clear: Optional function to clear parent IPI > >> > + * @ipi_mux_send: Trigger parent IPI on target CPUs > >> > + */ > >> > +struct ipi_mux_ops { > >> > + void (*ipi_mux_clear)(unsigned int parent_virq); > >> > + void (*ipi_mux_send)(unsigned int parent_virq, > >> > + const struct cpumask *mask); > >> > +}; > >> > + > >> > +void ipi_mux_process(void); > >> > +int ipi_mux_create(unsigned int parent_virq, unsigned int nr_ipi, > >> > + const struct ipi_mux_ops *ops); > >> > + > >> > #ifdef CONFIG_GENERIC_IRQ_MULTI_HANDLER > >> > /* > >> > * Registers a generic IRQ handling function as the top-level IRQ handler in > >> > diff --git a/kernel/irq/Kconfig b/kernel/irq/Kconfig > >> > index 10929eda9825..2388e7d40ed3 100644 > >> > --- a/kernel/irq/Kconfig > >> > +++ b/kernel/irq/Kconfig > >> > @@ -84,6 +84,10 @@ config GENERIC_IRQ_IPI > >> > bool > >> > select IRQ_DOMAIN_HIERARCHY > >> > > >> > +# Generic IRQ IPI Mux support > >> > +config GENERIC_IRQ_IPI_MUX > >> > + bool > >> > + > >> > # Generic MSI interrupt support > >> > config GENERIC_MSI_IRQ > >> > bool > >> > diff --git a/kernel/irq/Makefile b/kernel/irq/Makefile > >> > index b4f53717d143..f19d3080bf11 100644 > >> > --- a/kernel/irq/Makefile > >> > +++ b/kernel/irq/Makefile > >> > @@ -15,6 +15,7 @@ obj-$(CONFIG_GENERIC_IRQ_MIGRATION) += cpuhotplug.o > >> > obj-$(CONFIG_PM_SLEEP) += pm.o > >> > obj-$(CONFIG_GENERIC_MSI_IRQ) += msi.o > >> > obj-$(CONFIG_GENERIC_IRQ_IPI) += ipi.o > >> > +obj-$(CONFIG_GENERIC_IRQ_IPI_MUX) += ipi-mux.o > >> > obj-$(CONFIG_SMP) += affinity.o > >> > obj-$(CONFIG_GENERIC_IRQ_DEBUGFS) += debugfs.o > >> > obj-$(CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR) += matrix.o > >> > diff --git a/kernel/irq/ipi-mux.c b/kernel/irq/ipi-mux.c > >> > new file mode 100644 > >> > index 000000000000..bd6b31ca588b > >> > --- /dev/null > >> > +++ b/kernel/irq/ipi-mux.c > >> > @@ -0,0 +1,199 @@ > >> > +// SPDX-License-Identifier: GPL-2.0-only > >> > +/* > >> > + * Multiplex several virtual IPIs over a single HW IPI. > >> > + * > >> > + * Copyright (c) 2022 Ventana Micro Systems Inc. > >> > + */ > >> > + > >> > +#define pr_fmt(fmt) "ipi-mux: " fmt > >> > +#include > >> > +#include > >> > +#include > >> > +#include > >> > +#include > >> > +#include > >> > +#include > >> > + > >> > +static unsigned int ipi_mux_nr; > >> > +static unsigned int ipi_mux_parent_virq; > >> > +static struct irq_domain *ipi_mux_domain; > >> > +static const struct ipi_mux_ops *ipi_mux_ops; > >> > +static DEFINE_PER_CPU(unsigned long, ipi_mux_bits); > >> > + > >> > +static void ipi_mux_send_mask(struct irq_data *d, const struct cpumask *mask) > >> > +{ > >> > + int cpu; > >> > + > >> > + /* Barrier before doing atomic bit update to IPI bits */ > >> > + smp_mb__before_atomic(); > >> > + > >> > + for_each_cpu(cpu, mask) > >> > + set_bit(d->hwirq, per_cpu_ptr(&ipi_mux_bits, cpu)); > >> > + > >> > + /* Barrier after doing atomic bit update to IPI bits */ > >> > + smp_mb__after_atomic(); > >> > + > >> > + /* Trigger the parent IPI */ > >> > + ipi_mux_ops->ipi_mux_send(ipi_mux_parent_virq, mask); > >> > +} > >> > + > >> > +static const struct irq_chip ipi_mux_chip = { > >> > + .name = "IPI Mux", > >> > + .ipi_send_mask = ipi_mux_send_mask, > >> > >> I've given this a bit more though, and I came to the conclusion that > >> we really should have the full masking semantics here, even if Linux > >> currently doesn't really use it. > >> > >> It makes the handling a bit more complex, and unmasking a pending IPI > >> must be handled gracefully, but we already have implemented most of > >> that code in the irq-apple-aic driver. > >> > >> And if we go down this road, such a driver should be very easy to move > >> over this infrastructure, making the change a lot more palatable. > > > > Sounds good. > > > > I will send v8 of ipi-mux which can be easily adapted for irq-apple-aic > > driver > > and it will have masking semantics as well. > > Thanks. No hurry though, as I'm closing the queue for 5.20 (fixes > only until -rc1). Okay, I will send after 5.20-rc1. Regards, Anup > > Thanks, > > M. > -- > Jazz is not dead. It just smells funny...