Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4415159pxv; Tue, 29 Jun 2021 06:35:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxykrWiz1iMSeJ3LndLX9x+ZeHJvnG1xDvW1XyDY5jglXrxsNnvZXj9M5aDifkhjdVVl8wq X-Received: by 2002:a05:6402:34c1:: with SMTP id w1mr34252387edc.104.1624973744099; Tue, 29 Jun 2021 06:35:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624973744; cv=none; d=google.com; s=arc-20160816; b=PfmV8kH16E/YvGNJtDs5g4suHvgrqBnqmWIyRn6zTqZCEagnqHaN231nOt9EVFGjio igSP9m4ZSQeAn0Q1+Tugb1M+LiftSEwTVJGrbK65rRbscRmYNN2Z5mQjUNtl6LbsXeLy xarNj5xe8DxniLEyd5ooVr/Fu9yqj627l+lO4U7hS+bOwZEG4jL3QPpkL86ndziUpEhs sAp9mz/xj9RTulvNN8eT/IcCObHIVW9IwO9V3rvT48/GoVB9snR8KR1CES/SwM9rrjrL TLataf2Fikxgdwx9vBMBS9bjjaX4DSc1B4wv98spqkVZdb0sHfbVTm9dolv6drBM+qCi tq4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=r4FipyzlTI4ql+ZvuvU4MNPipqkrlOjJx5Nx6X4r3T8=; b=NmWCkYgVIUcTRo1x4iJ/rzkZjCn0V6V3ogWdOOGEIfEErMMRrr0lv1GAPqqQbEd0Ix srUL6SmGdaVJWHPUwovyexD7JwtlJr62w0eGPu6zpfgW/aAZ7OtsE7sSoFdFJOVuwsge tVRRoGUvXdn2Aw/M5hkQkwNTyOx2krvpGXbtmc1bbhq0+UycNLA4mSSkI9lYphRhXxRl hLG/1e8v2a/94diX5+6U4AU8TvEkqSsAj9zzvH6L+L9kqMQZNUC48ndA4Wr/ub9ma4Pd lzA9qmgZYsOChC9B0NP8qT6rDMmBHCI0cn7gsMH/Zvb4w+VAsXM2oAVLByJrxPTjpH8N 35Og== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id by10si17121770ejc.77.2021.06.29.06.35.20; Tue, 29 Jun 2021 06:35:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233832AbhF2MxT (ORCPT + 99 others); Tue, 29 Jun 2021 08:53:19 -0400 Received: from foss.arm.com ([217.140.110.172]:50362 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233161AbhF2MxN (ORCPT ); Tue, 29 Jun 2021 08:53:13 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7F4AE106F; Tue, 29 Jun 2021 05:50:46 -0700 (PDT) Received: from e113632-lin.cambridge.arm.com (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 7D3A73F718; Tue, 29 Jun 2021 05:50:45 -0700 (PDT) From: Valentin Schneider To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Marc Zyngier , Thomas Gleixner , Lorenzo Pieralisi , Vincenzo Frascino Subject: [PATCH v3 00/13] irqchip/irq-gic: Optimize masking by leveraging EOImode=1 Date: Tue, 29 Jun 2021 13:49:57 +0100 Message-Id: <20210629125010.458872-1-valentin.schneider@arm.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi folks! This is the spiritual successor to the below, which was over 6 years ago (!): https://lore.kernel.org/lkml/1414235215-10468-1-git-send-email-marc.zyngier@arm.com/ The series is available, along with my silly IRQ benchmark, at: https://git.gitlab.arm.com/linux-arm/linux-vs.git -b mainline/irq/eoimodness-v3 Revisions ========= RFCv2 -> v3 +++++++++++ o Rebased on top of tip/irq/core: 3d2ce675aba7 ("Merge tag 'irqchip-5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/core") o Tested with irqchip.gicv3_pseudo_nmi=1 using Marc's fixes (arm64/for-next/cpuidle) on Ampere eMAG and Ampere Altra. o Re-collected performance numbers for Juno and Ampere eMAG, also collected for Ampere Altra o Fixed s/irq_{ack, eoi}/{ack, eoi}_irq/ naming blunder (Marc) o Gave msi_domain_update_chip_ops() default .irq_ack() and .irq_eoi() (Marc) Marc had suggested implementing a default callback that scans the domain hierarchy for .irq_ack / .irq_eoi() and calls the first non-NULL one. Now, things like nexus domains already have an irq_chip_eoi_parent(); leaving this would defeat using a "smarter" version in child domains, and removing it felt like further obscuring the hierarchies. So just like turtles, I went with irq_chip_{ack, eoi}_parent() all the way down. o Added .irq_ack() callbacks to relevant GIC gadgets (Marc) There might still be something to be done wrt chip flags, but I'll leave that as it is for now. See my ramblings at: http://lore.kernel.org/r/87lf7bb1ek.mognet@arm.com RFCv1 -> RFCv2 ++++++++++++++ o Rebased against latest tip/irq/core o Applied cleanups suggested by Thomas o Collected some performance results Background ========== GIC mechanics +++++++++++++ There are three IRQ operations: o Acknowledge. This gives us the IRQ number that interrupted us, and also - raises the running priority of the CPU interface to that of the IRQ - sets the active bit of the IRQ o Priority Drop. This "clears" the running priority. o Deactivate. This clears the active bit of the IRQ. o The CPU interface has a running priority value. No interrupt of lower or equal priority will be signaled to the CPU attached to that interface. On Linux, we only have two priority values: pNMIs at highest priority, and everything else at the other priority. o Most GIC interrupts have an "active" bit. This bit is set on Acknowledge and cleared on Deactivate. A given interrupt cannot be re-signaled to a CPU if it has its active bit set (i.e. if it "fires" again while it's being handled). EOImode fun +++++++++++ In EOImode=0, Priority Drop and Deactivate are undissociable. The (simplified) interrupt handling flow is as follows: <~IRQ> Acknowledge Priority Drop + Deactivate With EOImode=1, we can invoke each operation individually. This gives us: <~IRQ> Acknowledge Priority Drop <*other* interrupts can be signaled from here, once interrupts are re-enabled> Deactivate <*this* interrupt can be signaled again> What this means is that with EOImode=1, any interrupt is kept "masked" by its active bit between Priority Drop and Deactivate. Threaded IRQs and ONESHOT ========================= ONESHOT threaded IRQs must remain masked between the main handler and the threaded handler. Right now we do this using the conventional irq_mask() operations, which looks like this: Acknowledge Priority Drop irq_mask() Deactivate irq_unmask() However, masking for the GICs means poking the distributor, and there's no sysreg for that - it's an MMIO access. We've seen above that our IRQ handling can give us masking "for free", and this is what this patch set is all about. It turns the above handling into: Acknowledge Priority Drop Deactivate No irq_mask() => fewer MMIO accesses => happier users (or so I've been told). This is especially relevant to PREEMPT_RT which forces threaded IRQs. Functional testing ================== GICv2 +++++ I've tested this on my Juno with forced irqthreads. This makes the pl011 IRQ into a threaded ONESHOT IRQ, so I spammed my keyboard into the console and verified via ftrace that there were no irq_mask() / irq_unmask() involved. GICv3 +++++ I've tested this on my Ampere eMAG, which uncovered "fun" interactions with the MSI domains. Did the same trick as the Juno with the pl011. With Marc's pNMI vs cpuidle fixes (arm64/for-next/cpuidle), I also got to test this against pNMIs on Ampere eMAG & Altra. Nothing to report here. Performance impact ================== Benchmark +++++++++ Finding a benchmark that leverages a force-threaded IRQ has proved to be somewhat of a pain, so I crafted my own. It's a bit daft, but so are most benchmarks (though this one might win a prize). Long story short, I'm picking an unused IRQ and have it be force-threaded. The benchmark then is: loop: irq_set_irqchip_state(irq, IRQCHIP_STATE_PENDING, true); wait_for_completion(&done); complete(&done); A more complete picture would be: raise IRQ wait run flow handler wake IRQ thread finish handling wake bench thread Letting this run for a fixed amount of time lets me measure an entire IRQ handling cycle, which is what I'm after since there's one less mask() in the flow handler and one less unmask() in the threaded handler. You'll note there's some potential "noise" in there due to scheduling both the benchmark thread and the IRQ thread. However, the IRQ thread is pinned to the IRQ's affinity, and I also pinned the benchmark thread in my tests, which should keep this noise to a minimum. Results +++++++ 20 iterations of 5 seconds of the above benchmark, measuring irqs/sec delta between tip/irq/core and the series: Juno r0: | mean | median | 90th percentile | 99th percentile | |------+--------+-----------------+-----------------| | +6% | +6% | +6% | +6% | Ampere eMAG: | mean | median | 90th percentile | 99th percentile | |------+--------+-----------------+-----------------| | +21% | +22% | +20% | +20% | Ampere Altra: | mean | median | 90th percentile | 99th percentile | |------+--------+-----------------+-----------------| | +22% | +22% | +22% | +22% | Cheers, Valentin Valentin Schneider (13): genirq: Add chip flag to denote automatic IRQ (un)masking genirq: Define ack_irq() and eoi_irq() helpers genirq: Employ ack_irq() and eoi_irq() where relevant genirq: Add handle_strict_flow_irq() flow handler genirq: Let purely flow-masked ONESHOT irqs through unmask_threaded_irq() genirq: Don't mask IRQ within flow handler if IRQ is flow-masked genirq, irq-gic-v3: Make NMI flow handlers use ->irq_ack() if available genirq/msi: Provide default .irq_eoi() for MSI chips irqchip/gic: Rely on MSI default .irq_eoi() genirq/msi: Provide default .irq_ack() for MSI chips irqchip/gic: Add .irq_ack() to GIC-based irqchips irqchip/gic: Convert to handle_strict_flow_irq() irqchip/gic-v3: Convert to handle_strict_flow_irq() drivers/base/platform-msi.c | 2 - drivers/irqchip/irq-gic-v2m.c | 2 +- drivers/irqchip/irq-gic-v3-its-fsl-mc-msi.c | 1 - drivers/irqchip/irq-gic-v3-its-pci-msi.c | 1 - drivers/irqchip/irq-gic-v3-its.c | 3 + drivers/irqchip/irq-gic-v3-mbi.c | 2 +- drivers/irqchip/irq-gic-v3.c | 27 +++-- drivers/irqchip/irq-gic.c | 14 ++- include/linux/irq.h | 15 ++- kernel/irq/chip.c | 122 +++++++++++++++++--- kernel/irq/debugfs.c | 2 + kernel/irq/internals.h | 7 ++ kernel/irq/manage.c | 2 +- kernel/irq/msi.c | 4 + 14 files changed, 166 insertions(+), 38 deletions(-) -- 2.25.1