Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp138738rwb; Thu, 12 Jan 2023 04:33:45 -0800 (PST) X-Google-Smtp-Source: AMrXdXs+YkKafg+psqKBrMM6HUp0ycHfIfdW85pNSM8VneyZQAj7fMIbUfVGbhtE2myCDCI6gr4M X-Received: by 2002:a17:907:1385:b0:7c1:6167:7816 with SMTP id vs5-20020a170907138500b007c161677816mr54628589ejb.28.1673526825755; Thu, 12 Jan 2023 04:33:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673526825; cv=none; d=google.com; s=arc-20160816; b=BRTVmdZFpweKLi1ePuPDzuhjHqdb4Cg4iE8C9HtALrL9wzJ+sQWmvUf/A7QgorTYmr rfmfWeFXdDnc1bpJrIwQukddHpE6jQr2/dFqoSkfmONGSnJEYrbxnnYOMXGLKr1xlu1F GpGK++S2/W5LMmSwocpN6Di/qOM1fjlOeX8Lj6HRgWp37kNEeANTsLvM9XZtsPoc/2JA SDKKpvvSYNE3QGHxoGsGSJDehYXhSL5wXx1K3c/nQo2Ne+aTY0OaB85/kmR+UuEHFwhN VvhUj4kCA1JxJquQL6NiSh4i8xQ/V91UCKVhI8Chlf0kLq+VyVjubjsWNd4CpqHshKdP QalQ== 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=3tzazKC6UXrwpt+mRZpio8Zio90a1gncXEmmy1/qn/g=; b=qvbNUlYhP4gRKjpq037F83FDIB6OJIbFBGShj1MLfWoUFmeLd/+HHyzDuZdEXG9luf JQ20EvVAAFlNIbvH7Ot0ERpY3/CzIl9JL4sdT+95SFMOZ/XC+T3oJfQLVouY1NPMx7Ox QanDdX2oK02yCVRFbCDxWgSyCCODlciTpwqIm2za3Kv73ENRUB4hBHg30wa4tT7+j5N6 HorH2oPEL8/av6MeM26JXR9kqxYQYnHlWIXx+mnhKPecxJdu9yHeAZ7yj4N95Bfn+Tdz sUXRdAz9wCVx6cY3ywWyY4Ssld6iFGJKk4oKHCGRh+X3+nTY7gJXmC8JONQwFr9Slx6G Qk/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b=QXlPITpk; 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 dp16-20020a170906c15000b0085b4d436b4csi7781103ejc.998.2023.01.12.04.33.33; Thu, 12 Jan 2023 04:33:45 -0800 (PST) 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=@ventanamicro.com header.s=google header.b=QXlPITpk; 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 S236524AbjALMUZ (ORCPT + 51 others); Thu, 12 Jan 2023 07:20:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236311AbjALMT6 (ORCPT ); Thu, 12 Jan 2023 07:19:58 -0500 Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1D9294C726 for ; Thu, 12 Jan 2023 04:17:59 -0800 (PST) Received: by mail-vs1-xe35.google.com with SMTP id 186so13537793vsz.13 for ; Thu, 12 Jan 2023 04:17:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3tzazKC6UXrwpt+mRZpio8Zio90a1gncXEmmy1/qn/g=; b=QXlPITpkSBUCEI5PoA2+D1w5R31w2E9UbHxWtXDXbfYMorSMtVl2qN3Z8MMbrMJ5aW Yxvk8A51ReEndAKVQumpL4ikqZwUwsv4dregUnMnYam1vBf0PoX4hkl5Lkgygw93FdGJ rIJGCOvloN+aBmV5R4zCbSLkkKOiyAN6iBa+9GUQaFTWyDXil5fE89pF+oBjAcbbxqiF hVho69zfR+sXxEKp3Z9rze+N6V1bpWljabVNqaSMzL1Hn9AlWVPtC25ZYrHTBjiUd6PK 4G9VKoUnCqFy/24KFbTkI5g3UGwqw+43eOLotgOJC3PfnomJZjSL56Ee2KysnE4/+85t a15g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3tzazKC6UXrwpt+mRZpio8Zio90a1gncXEmmy1/qn/g=; b=imzbg/CclFIGXuhdTRoQRVwdD4q/zOCnKxPNMNVJvCAazpsVmZondlJVlHss73lius hnrItucMJiGc601uRuwwGJubc5M7Y6E5FJlTM0zME/gCukJ3HMXI/XPI42BbanamzHc2 /lhgSlEI/xVQNkHN1ZHjrM2lXwiwTIWWZk0ogbL1BW0lTIZ9TkThBrsatjqeYaKqA/Bc gZ+mRdIe067zvdUw5xCofG/ZNikJBqHONPMh7PJZRxo3WrLYIR2vjvJB+7+XcY3jyzmZ 7wBf9DSKJTq4zybYgjH/20itsJzWn+pPDh80zsy+LZ/6p3aXCR4lUA0RO9Wigv44L4V8 Mbxg== X-Gm-Message-State: AFqh2kqZVflsxE2il6HY4Sqt2PzGNFxvm5aEm+qakfXUzF2JAo7x18Mr YHefmtLXVYyDPmodL3jP48mm3bdM6R+b82Gzu+yddg== X-Received: by 2002:a05:6102:55aa:b0:3be:ea71:5aaa with SMTP id dc42-20020a05610255aa00b003beea715aaamr10408899vsb.0.1673525878036; Thu, 12 Jan 2023 04:17:58 -0800 (PST) MIME-Version: 1.0 References: <20230103141221.772261-1-apatel@ventanamicro.com> In-Reply-To: <20230103141221.772261-1-apatel@ventanamicro.com> From: Anup Patel Date: Thu, 12 Jan 2023 17:47:46 +0530 Message-ID: Subject: Re: [PATCH v16 0/9] RISC-V IPI Improvements To: Marc Zyngier Cc: Hector Martin , Sven Peter , Alyssa Rosenzweig , Palmer Dabbelt , Paul Walmsley , Daniel Lezcano , Thomas Gleixner , Atish Patra , Alistair Francis , Anup Patel , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, asahi@lists.linux.dev Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS 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 Hi Marc, On Tue, Jan 3, 2023 at 7:42 PM Anup Patel wrote: > > This series aims to improve IPI support in Linux RISC-V in following ways: > 1) Treat IPIs as normal per-CPU interrupts instead of having custom RISC-V > specific hooks. This also makes Linux RISC-V IPI support aligned with > other architectures. > 2) Remote TLB flushes and icache flushes should prefer local IPIs instead > of SBI calls whenever we have specialized hardware (such as RISC-V AIA > IMSIC and RISC-V SWI) which allows S-mode software to directly inject > IPIs without any assistance from M-mode runtime firmware. > > These patches were originally part of the "Linux RISC-V ACLINT Support" > series but this now a separate series so that it can be merged independently > of the "Linux RISC-V ACLINT Support" series. > (Refer, https://lore.kernel.org/lkml/20211007123632.697666-1-anup.patel@wdc.com/) > > These patches are also a preparatory patches for the up-coming: > 1) Linux RISC-V AIA support > 2) Linux RISC-V SWI support > > These patches can also be found in riscv_ipi_imp_v16 branch at: > https://github.com/avpatel/linux.git > > Changes since v15: > - Rebased on Linux-6.2-rc2 > - Added Reviewed-by and Tested-by tags to some of the patches. > > Changes since v14: > - Minor fixes in commit description of PATCH3 (as suggested by tglx) > - Don't disable parent IPI when CPU goes offline for SBI IPI driver and > CLINT driver in PATCH4. > - Include Apple AIC driver changes from Marc Z as PATCH9 > > Changes since v13: > - Included changes suggested by Marc Z in PATCH3 > - Use chained handlers in PATCH4 > - Added new PATCH8 to have empty irq_eoi() in RISC-V INTC driver. This > avoids the unnecessary mask/unmask dance at time of handling interrupts. > > Changes since v12: > - Rebased on Linux-6.1-rc7 > - Bring-back the IPI optimization in ipi_mux_send_mask() for PATCH3 > - Call ipi_mux_send() for one target CPU at a time in PATCH3 > > Changes since v11: > - Removed ipi_mux_pre/post_handle() callbacks in PATCH3 > - Removed sturct ipi_mux_ops in PATCH3 > - Removed parent_virq and data pointer from everywhere in PATCH3 > - Removed struct ipi_mux_control in PATCH3 > - Improved function signature of ipi_mux_send() callback in PATCH3 > - Used unsigned type with atomic operation in PATCH3 > > Changes since v10: > - Rebased on Linux-6.1-rc5 > - Drop the "!(pending & ibit)" check in ipi_mux_send_mask() of PATCH3 > - Disable local interrupts in ipi_mux_send_mask() of PATCH3 because we > can be preempted while using a per-CPU temporary variable. > > Changes since v9: > - Rebased on Linux-6.1-rc3 > - Updated header comment block of ipi-mux.c in PATCH3 > - Use a struct for global data of ipi-mux.c in PATCH3 > - Add per-CPU temp cpumask for sending IPIs in PATCH3 > - Drop the use of fwspec in PATCH3 > - Use static key for ipi_mux_pre_handle() and ipi_mux_post_handle() > in PATCH3 > - Remove redundant pr_warn_ratelimited() called by ipi_mux_process() > in PATCH3 > - Remove CPUHP thingy from ipi_mux_create() in PATCH3 > > Changes since v8: > - Rebased on Linux-6.0-rc3 > - Use dummy percpu data as parameter for request_percpu_irq() in PATCH4. > > Changes since v7: > - Rebased on Linux-6.0-rc1 > - Use atomic operations to track per-CPU pending and enabled IPIs in PATCH3. > (Note: this is inspired from IPI muxing implemented in > drivers/irqchip/irq-apple-aic.c) > - Made "struct ipi_mux_ops" (added by PATCH3) flexible so that > drivers/irqchip/irq-apple-aic.c can adopt it in future. > > Changes since v6: > - Rebased on Linux-5.19-rc7 > - Added documentation for struct ipi_mux_ops in PATCH3 > - Dropped dummy irq_mask()/unmask() in PATCH3 > - Added const for "ipi_mux_chip" in PATCH3 > - Removed "type" initialization from ipi_mux_domain_alloc() in PATCH3 > - Dropped translate() from "ipi_mux_domain_ops" in PATCH3 > - Improved barrier documentation in ipi_mux_process() of PATCH3 > - Added percpu check in ipi_mux_create() for parent_virq of PATCH3 > - Added nr_ipi parameter in ipi_mux_create() of PATCH3 > > Changes since v5: > - Rebased on Linux-5.18-rc3 > - Used kernel doc style in PATCH3 > - Removed redundant loop in ipi_mux_process() of PATCH3 > - Removed "RISC-V" prefix form ipi_mux_chip.name of PATCH3 > - Removed use of "this patch" in PATCH3 commit description > - Addressed few other nit comments in PATCH3 > > Changes since v4: > - Rebased on Linux-5.17 > - Includes new PATCH3 which adds mechanism to multiplex a single HW IPI > > Changes since v3: > - Rebased on Linux-5.17-rc6 > - Updated PATCH2 to not export riscv_set_intc_hwnode_fn() > - Simplified riscv_intc_hwnode() in PATCH2 > > Changes since v2: > - Rebased on Linux-5.17-rc4 > - Updated PATCH2 to not create synthetic INTC fwnode and instead provide > a function which allows drivers to directly discover INTC fwnode > > Changes since v1: > - Use synthetic fwnode for INTC instead of irq_set_default_host() in PATCH2 > > Anup Patel (8): > RISC-V: Clear SIP bit only when using SBI IPI operations > irqchip/riscv-intc: Allow drivers to directly discover INTC hwnode > genirq: Add mechanism to multiplex a single HW IPI > RISC-V: Treat IPIs as normal Linux IRQs > RISC-V: Allow marking IPIs as suitable for remote FENCEs > RISC-V: Use IPIs for remote TLB flush when possible > RISC-V: Use IPIs for remote icache flush when possible > irqchip/riscv-intc: Add empty irq_eoi() for chained irq handlers > > Marc Zyngier (1): > irqchip/apple-aic: Move over to core ipi-mux > > arch/riscv/Kconfig | 2 + > arch/riscv/include/asm/irq.h | 4 + > arch/riscv/include/asm/sbi.h | 9 +- > arch/riscv/include/asm/smp.h | 49 +++++-- > arch/riscv/kernel/Makefile | 1 + > arch/riscv/kernel/cpu-hotplug.c | 3 +- > arch/riscv/kernel/irq.c | 21 ++- > arch/riscv/kernel/sbi-ipi.c | 77 +++++++++++ > arch/riscv/kernel/sbi.c | 100 +++------------ > arch/riscv/kernel/smp.c | 171 ++++++++++++------------ > arch/riscv/kernel/smpboot.c | 5 +- > arch/riscv/mm/cacheflush.c | 5 +- > arch/riscv/mm/tlbflush.c | 93 +++++++++++--- > drivers/clocksource/timer-clint.c | 65 +++++++--- > drivers/irqchip/Kconfig | 2 + > drivers/irqchip/irq-apple-aic.c | 161 ++--------------------- > drivers/irqchip/irq-riscv-intc.c | 71 ++++++---- > include/linux/irq.h | 3 + > kernel/irq/Kconfig | 5 + > kernel/irq/Makefile | 1 + > kernel/irq/ipi-mux.c | 207 ++++++++++++++++++++++++++++++ > 21 files changed, 654 insertions(+), 401 deletions(-) > create mode 100644 arch/riscv/kernel/sbi-ipi.c > create mode 100644 kernel/irq/ipi-mux.c > > -- > 2.34.1 > Friendly ping ? Regards, Anup