From: Jiri Slaby <jirislaby@kernel.org>
To: Eliav Farber <farbere@amazon.com>,
linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
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
Cc: jonnyc@amazon.com
Subject: Re: [PATCH v5 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation
Date: Wed, 4 Dec 2024 12:02:56 +0100 [thread overview]
Message-ID: <96cdb630-5c9e-4364-93fc-67f9ee34a403@kernel.org> (raw)
In-Reply-To: <20241130201143.48808-2-farbere@amazon.com>
On 30. 11. 24, 21:11, 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.
...
> --- a/kernel/irq/Kconfig
> +++ b/kernel/irq/Kconfig
> @@ -154,3 +154,12 @@ config DEPRECATED_IRQ_CPU_ONOFFLINE
> bool
> depends on CAVIUM_OCTEON_SOC
> default CAVIUM_OCTEON_SOC
> +
> +config GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD
> + bool "Clear forwarded VM interrupts during kexec"
> + default n
> + help
> + When enabled, this option allows the kernel to clear the active state
> + of interrupts that are forwarded to virtual machines (VMs) during a
> + machine kexec. For interrupts that are not forwarded, if supported,
> + the kernel will attempt to trigger an End of Interrupt (EOI).
This caught my attention. It looks like you want to allow people
toggling it? I believe only arch code should turn it on as you do by
"select", not users.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2024-12-04 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 20:11 [PATCH v5 0/2] Improve interrupt handling during machine kexec Eliav Farber
2024-11-30 20:11 ` [PATCH v5 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation Eliav Farber
2024-12-03 11:04 ` Thomas Gleixner
2024-12-04 11:02 ` Jiri Slaby [this message]
2024-11-30 20:11 ` [PATCH v5 2/2] kexec: Prevent redundant IRQ masking by checking state before shutdown Eliav Farber
[not found] <077908c5f02545f0a9e02ae77cbd771c@amazon.com>
2024-12-03 16:36 ` [PATCH v5 1/2] kexec: Consolidate machine_kexec_mask_interrupts() implementation Thomas Gleixner
[not found] <4192766c8f02494a82db68f5732c6dd2@amazon.com>
2024-12-04 14:07 ` Thomas Gleixner
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=96cdb630-5c9e-4364-93fc-67f9ee34a403@kernel.org \
--to=jirislaby@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 \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).