From: Will Deacon <will@kernel.org>
To: Eliav Farber <farbere@amazon.com>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, naveen@kernel.org,
maddy@linux.ibm.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, tglx@linutronix.de,
akpm@linux-foundation.org, bhe@redhat.com,
hbathini@linux.ibm.com, sourabhjain@linux.ibm.com,
adityag@linux.ibm.com, songshuaishuai@tinylab.org,
takakura@valinux.co.jp, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, jonnyc@amazon.com
Subject: Re: [PATCH v6 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation
Date: Mon, 27 Jan 2025 16:39:06 +0000 [thread overview]
Message-ID: <20250127163905.GC25757@willie-the-truck> (raw)
In-Reply-To: <20241204142003.32859-2-farbere@amazon.com>
On Wed, Dec 04, 2024 at 02:20:02PM +0000, Eliav Farber wrote:
> Consolidate the machine_kexec_mask_interrupts implementation into a common
> function located in a new file: kernel/irq/kexec.c. This removes duplicate
> implementations from architecture-specific files in arch/arm, arch/arm64,
> arch/powerpc, and arch/riscv, reducing code duplication and improving
> maintainability.
>
> The new implementation retains architecture-specific behavior for
> CONFIG_GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD, which was previously implemented
> for ARM64. When enabled (currently for ARM64), it clears the active state
> of interrupts forwarded to virtual machines (VMs) before handling other
> interrupt masking operations.
>
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> ---
> V5 -> V6:
> - Change GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD to not be user selectable.
>
> arch/arm/kernel/machine_kexec.c | 23 ------------------
> arch/arm64/Kconfig | 1 +
> arch/arm64/kernel/machine_kexec.c | 31 ------------------------
> arch/powerpc/include/asm/kexec.h | 1 -
> arch/powerpc/kexec/core.c | 22 -----------------
> arch/powerpc/kexec/core_32.c | 1 +
> arch/riscv/kernel/machine_kexec.c | 23 ------------------
> include/linux/irq.h | 3 +++
> kernel/irq/Kconfig | 6 +++++
> kernel/irq/Makefile | 2 +-
> kernel/irq/kexec.c | 40 +++++++++++++++++++++++++++++++
> 11 files changed, 52 insertions(+), 101 deletions(-)
> create mode 100644 kernel/irq/kexec.c
>
> diff --git a/arch/arm/kernel/machine_kexec.c b/arch/arm/kernel/machine_kexec.c
> index 80ceb5bd2680..dd430477e7c1 100644
> --- a/arch/arm/kernel/machine_kexec.c
> +++ b/arch/arm/kernel/machine_kexec.c
> @@ -127,29 +127,6 @@ void crash_smp_send_stop(void)
> cpus_stopped = 1;
> }
>
> -static void machine_kexec_mask_interrupts(void)
> -{
> - unsigned int i;
> - struct irq_desc *desc;
> -
> - for_each_irq_desc(i, desc) {
> - struct irq_chip *chip;
> -
> - chip = irq_desc_get_chip(desc);
> - if (!chip)
> - continue;
> -
> - if (chip->irq_eoi && irqd_irq_inprogress(&desc->irq_data))
> - chip->irq_eoi(&desc->irq_data);
> -
> - if (chip->irq_mask)
> - chip->irq_mask(&desc->irq_data);
> -
> - if (chip->irq_disable && !irqd_irq_disabled(&desc->irq_data))
> - chip->irq_disable(&desc->irq_data);
> - }
> -}
> -
> void machine_crash_shutdown(struct pt_regs *regs)
> {
> local_irq_disable();
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 100570a048c5..dcc3551cf6c2 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -149,6 +149,7 @@ config ARM64
> select GENERIC_IDLE_POLL_SETUP
> select GENERIC_IOREMAP
> select GENERIC_IRQ_IPI
> + select GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD
Is this really specific to VMs? In the new code, it's just controlling
this part of the old code:
> diff --git a/arch/arm64/kernel/machine_kexec.c b/arch/arm64/kernel/machine_kexec.c
> index 82e2203d86a3..6f121a0164a4 100644
> --- a/arch/arm64/kernel/machine_kexec.c
> +++ b/arch/arm64/kernel/machine_kexec.c
> @@ -207,37 +207,6 @@ void machine_kexec(struct kimage *kimage)
> BUG(); /* Should never get here. */
> }
>
> -static void machine_kexec_mask_interrupts(void)
> -{
> - unsigned int i;
> - struct irq_desc *desc;
> -
> - for_each_irq_desc(i, desc) {
> - struct irq_chip *chip;
> - int ret;
> -
> - chip = irq_desc_get_chip(desc);
> - if (!chip)
> - continue;
> -
> - /*
> - * First try to remove the active state. If this
> - * fails, try to EOI the interrupt.
> - */
> - ret = irq_set_irqchip_state(i, IRQCHIP_STATE_ACTIVE, false);
which is about active interrupts. Why can't that happen for the host?
Will
next prev parent reply other threads:[~2025-01-27 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 14:20 [PATCH v6 0/2] Improve interrupt handling during machine kexec Eliav Farber
2024-12-04 14:20 ` [PATCH v6 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation Eliav Farber
2025-01-27 16:39 ` Will Deacon [this message]
2024-12-04 14:20 ` [PATCH v6 2/2] kexec: Prevent redundant IRQ masking by checking state before shutdown Eliav Farber
2025-02-03 19:15 ` [PATCH v6 0/2] Improve interrupt handling during machine kexec patchwork-bot+linux-riscv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250127163905.GC25757@willie-the-truck \
--to=will@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=farbere@amazon.com \
--cc=hbathini@linux.ibm.com \
--cc=jonnyc@amazon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=songshuaishuai@tinylab.org \
--cc=sourabhjain@linux.ibm.com \
--cc=takakura@valinux.co.jp \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox