Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
	linux-arm-kernel@lists.infradead.org, kirill@shutemov.name
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
	lpieralisi@kernel.org, liaochang1@huawei.com,
	ashok.raj@oss.qualcomm.com, maz@kernel.org, will@kernel.org
Subject: Re: [PATCH v2 00/39] arm64: Add support for FEAT_NMI
Date: Thu, 19 Nov 2026 14:50:50 +0000	[thread overview]
Message-ID: <d4bb2979-4bc2-436c-8f4a-c9a5decea900@arm.com> (raw)
In-Reply-To: <38d04e8b-2f31-4616-8a8e-2747c7ce114d@huawei.com>

Hi Jinjie,

On 11/19/26 12:45, Jinjie Ruan wrote:
> 
> 在 2026/11/19 18:14, Vladimir Murzin 写道:
>> Hi Jinjie,
> Hi Vladimir,
> 
>> On 11/19/26 01:54, Jinjie Ruan wrote:
>>> 在 2026/11/18 20:17, Jinjie Ruan 写道:
>>>> Hi Vladimir,
>>>>
>>>> I gave the series a test on a Kunpeng HIP12 machine with 384 CPUs,
>>>> GICv4.2, firmware with SDEI event 0. The PE implements FEAT_NMI and the
>>>> GIC implements FEAT_GICv3_NMI.
>>>>
>>>> Tested-by: Jinjie Ruan <ruanjinjie@huawei.com>
>>>>
>>>> Rather than a single boot, I varied the four dimensions that select a
>>>> different masking path:
>>>>
>>>>   - PE FEAT_NMI       : present / masked with id_aa64pfr1.nmi=0
>>>>   - GIC superpriority : present / disabled
>>>>   - Pseudo-NMI        : irqchip.gicv3_pseudo_nmi=0/1
>>>>   - SDEI cross-CPU    : firmware event 0 active / disabled
>>> Hi Vladimir,
>>>
>>> It appears that SDEI cross-CPU has more issues. On our 384-CPU HIP12
>>> with SDEI event 0 active, a single
>>>
>>>       echo l > /proc/sysrq-trigger
>>>
>>> stuck the machine. Concretely, we see:
>>>
>>> - only 8-23 of the 384 CPUs answer the broadcast, the rest never do;
>>>
>>> - the framework's 10-second wait then expires for them:
>>>
>>>   After 10 seconds, these CPUS still haven't responded to the NMI:
>>>   3-9,11-45,47-261,263-339,341-351,353-383
>>>
>>> - the hardlockup detector fires on the stuck CPUs one watchdog
>>>   period later, and with hardlockup_panic=1 the box panics:
>>>
>>>   watchdog: CPU9: Watchdog detected hard LOCKUP on cpu 9
>>>   Kernel panic - not syncing: Hard LOCKUP
>>>
>>> - the stop escalation cannot rescue it either:
>>>
>>>    SMP: retry stop with SDEI NMI for CPUs 194
>>>    SMP: failed to stop secondary CPUs 194
>>>
>>>   so kdump reports "Some CPUs may be stale, kdump will be unreliable".
>>>
>>> The same kernel booted with sdei_nmi.disabled=1 answers 384/384 in 47-60
>>> ms with no warnings at all, and a single-target SDEI backtrace is fine
>>> at ~14 ms -- so what breaks is the broadcast form specifically, not SDEI
>>> delivery as such.
>>>
>> Thanks for testing!
>>
>> Just checking, do you run with irqchip.gicv3_pseudo_nmi=1? Ada has posted
>> fixes around SDEI few days ago [1].
> Not set irqchip.gicv3_pseudo_nmi=1.
> 
>> Also are you able to reproduce issue on mainline v7.4-rc3 (it should contain
>> recent fixes for SDEI [2] IIUC) to rule out interaction with patch series?
> With rc3, it seems more serious:
> 
> 1. Zero response: In rc2, 8 to 23 CPUs responded, while in rc3, none of
> them responded.
> 
> 2. Degraded to individual waiting: The RCU stall processor sends an NMI
> to each CPU individually and waits for 10 seconds for each CPU. It would
> take up to 64 minutes to complete the process for all 384 CPUs.
> 
> 3. System-wide stall: All CPUs from 1 to 383 were behind by GPs, and
> there were false positives. This indicates that the NMIs were not
> delivered at all, and even the detector itself was unsure about it.
> 
> 
>   [2016.403860][C108] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
>   [2016.558719][C108] rcu:  1-...!: (8 GPs behind)  idle=f3f0/0/0x0 ...
> (false positive?)
>      ... CPU 1–383 all list
>   [2020.349834][C108] rcu: (detected by 108, t=27240 jiffies, g=282629,
> q=5629 ncpus=384)
> 
>   [2020.358151][C108] Sending NMI from CPU 108 to CPUs 1:
>   [2030.364071][C108] After 10 seconds, these CPUS still haven't
> responded to the NMI: 1
>   [2030.371978][C108] Sending NMI from CPU 108 to CPUs 2:
>   [2040.377893][C108] After 10 seconds, these CPUS still haven't
> responded to the NMI: 2
> 
> 

Any chance you can attach debugger or collect traces so we know what those
CPUs are doing?

Vladimir

>> Thanks
>> Vladimir
>>
>> [1] https://lore.kernel.org/linux-arm-kernel/20261117174814.95936-1-ada.coupriediaz@arm.com/
>> [2] https://lore.kernel.org/all/20261105120835.3321912-1-kirill@shutemov.name/
>>
>>> Best regards,
>>> Jinjie
>>>
>>>> The last one needs a patch to switch attached at the end.
>>>>
>>>> # The Results are as below:
>>>>
>>>>   Grp  PE GIC pse SDEI | supports active pseudo IRQS_NMI fast  result
>>>>   ------------------------------------------------------------------
>>>>   A    y  y   n   y    |   1       1      0        4      y     PASS
>>>>   A2   y  y   n   n    |   1       1      0        4      y     PASS
>>>>   A3   y  y   y   n    |   1       0      1        4      y     PASS
>>>>   B    y  y   y   y    |   1       0      1        4      y     PASS
>>>>   C    n  y   n   y    |   0       0      0        4      y     PASS
>>>>   D    n  y   y   y    |   0       0      1        4      y     PASS
>>>>   E    y  y   n   y    |   0       0      0        0      y *   PASS
>>>>   F    y  n   n   y    |   1       1      0        0      n     PASS
>>>>   G    y  n   n   n    |   0       0      0        0      n     PASS
>>>>   H    y  n   y   n    |   0       0      1        4      y     PASS
>>>>
>>>>   supports     system_supports_nmi()
>>>>   active       system_uses_nmi()
>>>>   pseudo       system_uses_irq_prio_masking()
>>>>   IRQS_NMI     IRQ descriptors with IRQS_NMI set (IPIs + arm-pmu)
>>>>   fast         cpumask_backtrace() at a CPU spinning with local IRQs
>>>>                disabled returns in ms (NMI delivered) rather than
>>>>                ~1.5 s (plain IPI)
>>>>
>>>> ## IRQS_NMI is 4 means 4 types of NMI Interrupt Tests:
>>>>
>>>>      IRQ  hwirq      purpose
>>>>     ---------------------------------------------------------------
>>>>       4   0x3  SGI   IPI_CPU_STOP_NMI - stop a CPU on panic
>>>>       7   0x6  SGI   IPI_KGDB_ROUNDUP - kgdb roundup
>>>>       8   0x7  SGI   IPI_CPU_BACKTRACE - hardlockup all-CPU backtrace
>>>>      42   0x17 PPI   arm-pmu (PMUv3) - perf sampling
>>>>
>>>>
>>>>   * E is CONFIG_ARM64_NMI=n plus SDEI. "fast" there comes from SDEI,
>>>>     not from the architected path; IRQS_NMI=0 says so.
>>>>
>>>> # Checks that run on every boot and pass in all applicable groups:
>>>>
>>>>   irqflags / exception state
>>>>       save, restore and nesting round trip for DAIF, PMR and ALLINT;
>>>>       arch_irqs_disabled_flags() takes ALLINT into account;
>>>>       local_irq_disable() leaves ALLINT clear, and an NMI is still
>>>>       delivered inside that window.
>>>>
>>>>   exception contexts
>>>>       arm64_exc_hwstate_of_context() for PROCESS / NOIRQ / NONMI /
>>>>       ERROR / CRITICAL, including that CRITICAL sets ALLINT and NOIRQ
>>>>       does not; local_exceptions_save_mask()/restore() for NOIRQ and
>>>>       CRITICAL; local_exceptions_force_daif_save()/restore() on the
>>>>       idle/WFI path (pseudo-NMI only).
>>>>
>>>>   pstate
>>>>       regs_irqs_disabled() honours PSR_ALLINT_BIT; the bit survives the
>>>>       ptrace path.
>>>>
>>>>   kprobes
>>>>       registering a probe does not disturb ALLINT, including when it is
>>>>       set (so an NMI cannot become deliverable inside a probe); a probe
>>>>       on the real "msr allint" / "mrs xN, allint" instruction is
>>>>       rejected with -EINVAL.
>>>>
>>>>   adjacent subsystems
>>>>       an EFI runtime call does not clobber ALLINT; perf events keep
>>>>       counting across an ALLINT toggle.
>>>>
>>>>   genirq
>>>>       add_interrupt_randomness() is never called in NMI context.
>>>>
>>>>   CPU stop
>>>>       spin one CPU with IRQs disabled, then panic: the stop escalation
>>>>       reaches the NMI rung, "SMP: retry stop with NMI for CPUs 0".
>>>>
>>>> # The problem
>>>>
>>>> SDEI wins over the architected IPI path, unconditionally
>>>>
>>>> arch_trigger_cpumask_backtrace() returns as soon as
>>>> sdei_nmi_trigger_cpumask_backtrace() succeeds, so on a platform where
>>>> firmware offers SDEI event 0 the irqchip NMI path is never reached.
>>>>
>>>> More importantly PSTATE.ALLINT has no effect on the backtrace:
>>>>
>>>>     SDEI active   : cpumask_backtrace() returns in ~14 ms with ALLINT set
>>>>     SDEI disabled : the same call takes ~1.5 s   with ALLINT set
>>>>
>>>> That is, the NMI delivered by SDEI bypasses the PSTATE.ALLINT masking
>>>> (the interruption is cleared within 14 ms). The NMI that goes through
>>>> the GIC superpriority is restricted by ALLINT (the masking is cleared
>>>> after 1.5s).
>>>>
>>>> And there is no equivalent of "irqchip.gicv3_pseudo_nmi=" for SDEI NMI.
>>>>
>>>> The patch used for the SDEI switch is as below.
>>>>
>>>> Best regards,
>>>> Jinjie
>>>>
>>>> diff --git a/drivers/firmware/arm_sdei_nmi.c
>>>> b/drivers/firmware/arm_sdei_nmi.c
>>>> index 038eb79e28ac..22e8c3e7aa75 100644
>>>> --- a/drivers/firmware/arm_sdei_nmi.c
>>>> +++ b/drivers/firmware/arm_sdei_nmi.c
>>>> @@ -62,6 +62,24 @@
>>>>
>>>>  static bool sdei_nmi_available;
>>>>
>>>> +static bool sdei_nmi_disabled __ro_after_init;
>>>> +
>>>> +static int __init sdei_nmi_disable_setup(char *str)
>>>> +{
>>>> +       return kstrtobool(str, &sdei_nmi_disabled);
>>>> +}
>>>> +early_param("sdei_nmi.disabled", sdei_nmi_disable_setup);
>>>> +
>>>>  #define SDEI_NMI_EVENT                 0
>>>>
>>>>  /*
>>>> @@ -168,7 +186,7 @@ static void sdei_nmi_raise_backtrace(cpumask_t *mask)
>>>>   */
>>>>  bool sdei_nmi_trigger_cpumask_backtrace(const cpumask_t *mask, int
>>>> exclude_cpu)
>>>>  {
>>>> -       if (!sdei_nmi_available)
>>>> +       if (!sdei_nmi_available || sdei_nmi_disabled)
>>>>                 return false;
>>>>
>>>>         nmi_trigger_cpumask_backtrace(mask, exclude_cpu,
>>>> @@ -194,6 +212,9 @@ void sdei_nmi_stop_cpus(const cpumask_t *mask)
>>>>  {
>>>>         unsigned int cpu;
>>>>
>>>> +       if (sdei_nmi_disabled)
>>>> +               return;
>>>> +
>>>>         WRITE_ONCE(sdei_nmi_stopping, true);
>>>>
>>>>         /*
>>>> @@ -238,6 +259,10 @@ static int __init sdei_nmi_init(void)
>>>>         }
>>>>
>>>>         sdei_nmi_available = true;
>>>> +       if (sdei_nmi_disabled) {
>>>> +               pr_info("Sdei nmi disabled by sdei_nmi.disabled\n");
>>>> +               return 0;
>>>> +       }
>>>>         pr_info("using SDEI cross-CPU NMI (SDEI_EVENT_SIGNAL, event %u)\n",
>>>>                 SDEI_NMI_EVENT);
>>>>
>>>> 在 2026/11/12 21:20, Vladimir Murzin 写道:
>>>>> FEAT_NMI provides an architected mechanism for supporting non-maskable
>>>>> interrupts (NMIs) and less-masked interrupts (LMIs).
>>>>>
>>>>> Since we already support pseudo-NMIs via priority masking, introducing
>>>>> another flavour of NMI on top of the existing infrastructure could
>>>>> easily become messy, making the code harder to follow and reason
>>>>> about.
>>>>>
>>>>> To avoid that, this series first makes room for the new NMI "tenant"
>>>>> by restructuring the existing exception masking logic.
>>>>>
>>>>> The main idea is to separate the logical view of exception state from
>>>>> its hardware representation. To achieve this, we introduce logical
>>>>> exception contexts that can be mapped onto the corresponding hardware
>>>>> state. This naturally consolidates the hardware-specific handling into
>>>>> a small number of places, while allowing the rest of the code to
>>>>> operate purely in terms of logical exception contexts.
>>>>>
>>>>> Since this restructuring is non-trivial and carries a risk of subtle
>>>>> behavioural changes, the series adds extensive debug checks to verify
>>>>> that the hardware state always matches the expected logical state.
>>>>>
>>>>> With this restructuring in place, wiring FEAT_NMI into the new
>>>>> framework becomes much more manageable. GIC support for NMI is build
>>>>> on top.
>>>>>
>>>>> This work would not have been possible without the contributions of
>>>>> Ada Couprie Diaz, Mark Brown, and Lorenzo Pieralisi - please credit
>>>>> them for everything that works well. Any remaining bugs or issues are
>>>>> entirely my own.
>>>>>
>>>>> Most of the testing has been done on QEMU, Fast Model and pre-silicon
>>>>> environment, so the series definitely benefit from extensive testing
>>>>> on real hardware (without NMI, with pseudo-NMI, and with FEAT_NMI).
>>>>>
>>>>> Patches are organized as follow
>>>>>
>>>>> 1 - 15
>>>>>   Rework of existing pseudo-NMI logic to make room for FEAT_NMI
>>>>>
>>>>> 16 - 33
>>>>>   FEAT_NMI support including some preparation patches which have
>>>>>   no dependencies:
>>>>>     - efi/runtime-wrappers: Permit architectures to override IRQ flags checks
>>>>>     - arm64: smp: Abstract SGI and LPI operations
>>>>>
>>>>> 34 - 35
>>>>>   GICv3 support for NMI
>>>>>
>>>>> 36 - 39
>>>>>   GICv5 support for NMI (including some preparation patches)
>>>>>
>>>>> Changelog
>>>>>
>>>>>   v1 -> v2
>>>>>
>>>>>     - Rebased on v7.4-rc2
>>>>>     - Select HAVE_PERF_EVENTS_NMI when FEAT_NMI is enabled
>>>>>     - Reworked APEI SEA handling to mask exceptions sequentially   
>>>>>     - Updated GICv3 initialization to clear NMI configuration
>>>>>     - Added Tested-by and Reviewed-by tags where approriate
>>>>>     - Droped tags due to meaningful changes for:
>>>>>       + "arm64: replace local_daif helpers"
>>>>>       + "irqchip/gic-v3: Implement FEAT_GICv3_NMI support"
>>>>>
>>>>>   RFC v2 -> v1
>>>>>
>>>>>     - Rebased on v7.3-rc3.
>>>>>     - Dropped RFC tag, have not received objections, at the same time
>>>>>       got support from Jinjie
>>>>>     - Dropped prerequisite patches already present in the newer base
>>>>>     - Added logic to reject probing/stepping over ALLINT
>>>>>     - Moved addition of arm64_debug_exc_context() in separate patch
>>>>>     - Reworked debug logic for validating direction of exception
>>>>>       transition
>>>>>     - Split support for NMI in GICv5 in 3 separate patches
>>>>>     - Added review tags
>>>>>
>>>>>   RFC v1 -> RFC v2
>>>>>
>>>>>     - Rebased on v7.2-rc5.
>>>>>     - Improved commit descriptions.
>>>>>     - Split some patches into smaller ones.
>>>>>     - Added a graceful fallback for IPI requests when FEAT_NMI is
>>>>>       supported by the CPU but unsupported by the interrupt
>>>>>       controller.
>>>>>     - Split the GICv3 preparation from the FEAT_GICv3_NMI
>>>>>       implementation.
>>>>>     - Added NMI support to GICv5, primarily as an illustration of the
>>>>>       implementation, although it also happens to work on Fast Model.
>>>>>     - Added review tags only to unchanged patches. Review tags were
>>>>>       intentionally dropped from modified patches to reflect those
>>>>>       changes and encourage re-review.
>>>>>
>>>>> RFC v1:
>>>>>   https://lore.kernel.org/linux-arm-kernel/20260709121333.23507-1-vladimir.murzin@arm.com/
>>>>>
>>>>> RFC v2:
>>>>>   https://lore.kernel.org/linux-arm-kernel/20260727163453.7969-1-vladimir.murzin@arm.com/
>>>>>
>>>>> v1:
>>>>>   https://lore.kernel.org/linux-arm-kernel/20260914102102.68597-1-vladimir.murzin@arm.com/
>>>>>
>>>>> Thanks!
>>>>> Vladimir
>>>>>
>>>>> Ada Couprie Diaz (15):
>>>>>   arm64: irqflags: Introduce arm64-specific irqflags type
>>>>>   arm64: irqflags: save and use both DAIF and PMR
>>>>>   arm64: interrupts: Add common exception state helpers
>>>>>   arm64: entry: Introduce entry specific exception masking helpers
>>>>>   arm64: entry: replace DAIF helpers with entry helpers
>>>>>   arm64: interrupts: Introduce exception masking save/restore helpers
>>>>>   arm64: interrupts: introduce a helper for GIC priority initialization
>>>>>   arm64: replace local_daif helpers
>>>>>   arm64: cpuidle: use new helpers to bypass interrupt priority masking
>>>>>   arm64: remove daifflags.h
>>>>>   arm64: gicv3: remove GIC_PRIO_PSR_I_SET
>>>>>   arm64: ptrace: Add PSR_ALLINT_BIT
>>>>>   arm64: cpufeature: Detect PE support for FEAT_NMI
>>>>>   arm64: nmi: Manage masking for superpriority interrupts
>>>>>   arm64: irq: Report FEAT_NMI masking local IRQs
>>>>>
>>>>> Lorenzo Pieralisi (2):
>>>>>   irqchip/gic-v3: Rename nmi to pseudo_nmi
>>>>>   irqchip/gic-v3: Implement FEAT_GICv3_NMI support
>>>>>
>>>>> Mark Brown (5):
>>>>>   arm64: booting: Document boot requirements for FEAT_NMI
>>>>>   arm64: sysreg: Add definitions for immediate versions of MSR ALLINT
>>>>>   arm64: idreg: Add an override for FEAT_NMI
>>>>>   arm64: nmi: Add handling of superpriority interrupts as NMIs
>>>>>   arm64: nmi: Add Kconfig for NMI
>>>>>
>>>>> Vladimir Murzin (17):
>>>>>   arm64: process: Lift check for exception state to generic
>>>>>     infrastructure
>>>>>   arm64: cpufeature: Remove system_has_prio_mask_debugging()
>>>>>   arm64: irqflags: Switch to CONFIG_DEBUG_IRQFLAGS
>>>>>   arm64: Kconfig: Remove CONFIG_ARM64_DEBUG_PRIORITY_MASKING
>>>>>   efi/runtime-wrappers: Permit architectures to override IRQ flags
>>>>>     checks
>>>>>   arm64/efi: Implement override for IRQ flags checks
>>>>>   arm64: probes: Reject stepping over ALLINT
>>>>>   arm64: suspend: Always initialise PSTATE.ALLINT
>>>>>   arm64/efi: Add ALLINT to IRQ flags checks
>>>>>   arm64: kprobes: Disable NMIs
>>>>>   arm64: smp: Abstract SGI and LPI operations
>>>>>   arm64: smp: Fall back to IRQ when IPI NMI request fails
>>>>>   arm64: nmi: Select HAVE_PERF_EVENTS_NMI for FEAT_NMI
>>>>>   arm64: smp: Add NMI support for LPI-backed IPIs
>>>>>   genirq: Trust local irqchip when considering IRQ for NMI
>>>>>   genirq: Do not call add_interrupt_randomness() in NMI context
>>>>>   irqchip/gic-v5: Add NMI support
>>>>>
>>>>>  Documentation/arch/arm64/booting.rst          |   6 +
>>>>>  arch/arm64/Kconfig                            |  31 +-
>>>>>  arch/arm64/include/asm/assembler.h            |  20 +-
>>>>>  arch/arm64/include/asm/cpucaps.h              |   2 +
>>>>>  arch/arm64/include/asm/cpufeature.h           |  14 +-
>>>>>  arch/arm64/include/asm/cpuidle.h              |  18 +-
>>>>>  arch/arm64/include/asm/daifflags.h            | 144 --------
>>>>>  arch/arm64/include/asm/efi.h                  |  42 ++-
>>>>>  arch/arm64/include/asm/entry-common.h         |   8 +-
>>>>>  arch/arm64/include/asm/insn.h                 |   1 +
>>>>>  .../include/asm/interrupts/common_flags.h     | 255 +++++++++++++
>>>>>  arch/arm64/include/asm/interrupts/entry.h     | 102 ++++++
>>>>>  arch/arm64/include/asm/interrupts/masking.h   | 166 +++++++++
>>>>>  arch/arm64/include/asm/irqflags.h             | 150 ++++----
>>>>>  arch/arm64/include/asm/kvm_host.h             |   1 -
>>>>>  arch/arm64/include/asm/mmu_context.h          |   1 -
>>>>>  arch/arm64/include/asm/ptrace.h               |  25 +-
>>>>>  arch/arm64/include/asm/sysreg.h               |   2 +
>>>>>  arch/arm64/include/uapi/asm/ptrace.h          |   1 +
>>>>>  arch/arm64/kernel/acpi.c                      |  43 +--
>>>>>  arch/arm64/kernel/cpufeature.c                |  68 +++-
>>>>>  arch/arm64/kernel/debug-monitors.c            |   1 -
>>>>>  arch/arm64/kernel/entry-common.c              | 335 +++++++++++++-----
>>>>>  arch/arm64/kernel/entry.S                     |  14 +-
>>>>>  arch/arm64/kernel/hibernate.c                 |  14 +-
>>>>>  arch/arm64/kernel/hw_breakpoint.c             |  16 +-
>>>>>  arch/arm64/kernel/irq.c                       |  45 ++-
>>>>>  arch/arm64/kernel/machine_kexec.c             |   4 +-
>>>>>  arch/arm64/kernel/pi/idreg-override.c         |   1 +
>>>>>  arch/arm64/kernel/probes/decode-insn.c        |  11 +-
>>>>>  arch/arm64/kernel/probes/kprobes.c            |  24 +-
>>>>>  arch/arm64/kernel/process.c                   |  24 +-
>>>>>  arch/arm64/kernel/setup.c                     |   4 +-
>>>>>  arch/arm64/kernel/signal.c                    |   1 -
>>>>>  arch/arm64/kernel/smp.c                       | 217 ++++++++----
>>>>>  arch/arm64/kernel/suspend.c                   |  14 +-
>>>>>  arch/arm64/kernel/traps.c                     |   1 -
>>>>>  arch/arm64/kvm/hyp/nvhe/switch.c              |   2 +-
>>>>>  arch/arm64/kvm/hyp/vgic-v3-sr.c               |   7 +-
>>>>>  arch/arm64/kvm/hyp/vhe/switch.c               |  14 +-
>>>>>  arch/arm64/mm/fault.c                         |   1 -
>>>>>  arch/arm64/mm/mmu.c                           |   7 +-
>>>>>  arch/arm64/tools/cpucaps                      |   2 +
>>>>>  drivers/firmware/efi/runtime-wrappers.c       |  32 +-
>>>>>  drivers/irqchip/irq-gic-v3.c                  | 145 +++++++-
>>>>>  drivers/irqchip/irq-gic-v5.c                  | 244 ++++++++++++-
>>>>>  include/linux/irq.h                           |   2 +-
>>>>>  include/linux/irqchip/arm-gic-v3-prio.h       |   8 -
>>>>>  include/linux/irqchip/arm-gic-v3.h            |   4 +
>>>>>  kernel/irq/handle.c                           |   3 +-
>>>>>  kernel/irq/manage.c                           |   5 -
>>>>>  51 files changed, 1696 insertions(+), 606 deletions(-)
>>>>>  delete mode 100644 arch/arm64/include/asm/daifflags.h
>>>>>  create mode 100644 arch/arm64/include/asm/interrupts/common_flags.h
>>>>>  create mode 100644 arch/arm64/include/asm/interrupts/entry.h
>>>>>  create mode 100644 arch/arm64/include/asm/interrupts/masking.h
>>>>>



  reply	other threads:[~2026-11-19 14:51 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 13:20 [PATCH v2 00/39] arm64: Add support for FEAT_NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 01/39] arm64: irqflags: Introduce arm64-specific irqflags type Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 02/39] arm64: irqflags: save and use both DAIF and PMR Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 03/39] arm64: interrupts: Add common exception state helpers Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 04/39] arm64: process: Lift check for exception state to generic infrastructure Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 05/39] arm64: entry: Introduce entry specific exception masking helpers Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 06/39] arm64: entry: replace DAIF helpers with entry helpers Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 07/39] arm64: interrupts: Introduce exception masking save/restore helpers Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 08/39] arm64: interrupts: introduce a helper for GIC priority initialization Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 09/39] arm64: replace local_daif helpers Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 10/39] arm64: cpuidle: use new helpers to bypass interrupt priority masking Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 11/39] arm64: remove daifflags.h Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 12/39] arm64: gicv3: remove GIC_PRIO_PSR_I_SET Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 13/39] arm64: cpufeature: Remove system_has_prio_mask_debugging() Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 14/39] arm64: irqflags: Switch to CONFIG_DEBUG_IRQFLAGS Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 15/39] arm64: Kconfig: Remove CONFIG_ARM64_DEBUG_PRIORITY_MASKING Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 16/39] efi/runtime-wrappers: Permit architectures to override IRQ flags checks Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 17/39] arm64/efi: Implement override for " Vladimir Murzin
2026-11-13 13:22   ` Mark Brown
2026-11-12 13:20 ` [PATCH v2 18/39] arm64: booting: Document boot requirements for FEAT_NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 19/39] arm64: sysreg: Add definitions for immediate versions of MSR ALLINT Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 20/39] arm64: probes: Reject stepping over ALLINT Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 21/39] arm64: ptrace: Add PSR_ALLINT_BIT Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 22/39] arm64: idreg: Add an override for FEAT_NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 23/39] arm64: cpufeature: Detect PE support " Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 24/39] arm64: nmi: Manage masking for superpriority interrupts Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 25/39] arm64: irq: Report FEAT_NMI masking local IRQs Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 26/39] arm64: nmi: Add handling of superpriority interrupts as NMIs Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 27/39] arm64: suspend: Always initialise PSTATE.ALLINT Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 28/39] arm64/efi: Add ALLINT to IRQ flags checks Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 29/39] arm64: kprobes: Disable NMIs Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 30/39] arm64: smp: Abstract SGI and LPI operations Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 31/39] arm64: smp: Fall back to IRQ when IPI NMI request fails Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 32/39] arm64: nmi: Add Kconfig for NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 33/39] arm64: nmi: Select HAVE_PERF_EVENTS_NMI for FEAT_NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 34/39] irqchip/gic-v3: Rename nmi to pseudo_nmi Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 35/39] irqchip/gic-v3: Implement FEAT_GICv3_NMI support Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 36/39] arm64: smp: Add NMI support for LPI-backed IPIs Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 37/39] genirq: Trust local irqchip when considering IRQ for NMI Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 38/39] genirq: Do not call add_interrupt_randomness() in NMI context Vladimir Murzin
2026-11-12 13:20 ` [PATCH v2 39/39] irqchip/gic-v5: Add NMI support Vladimir Murzin
2026-11-14  5:03 ` [PATCH v2 00/39] arm64: Add support for FEAT_NMI Ashok Raj
2026-11-19 11:18   ` Vladimir Murzin
2026-11-16  6:58 ` Jinjie Ruan
2026-11-16 10:02   ` Vladimir Murzin
2026-11-16 11:01     ` Jinjie Ruan
2026-11-18 13:22       ` Vladimir Murzin
2026-11-19  2:33         ` Jinjie Ruan
2026-11-18 12:17 ` Jinjie Ruan
2026-11-19  1:54   ` Jinjie Ruan
2026-11-19 10:14     ` Vladimir Murzin
2026-11-19 12:45       ` Jinjie Ruan
2026-11-19 14:50         ` Vladimir Murzin [this message]
2026-11-19 11:41   ` Jinjie Ruan
2026-11-19 14:46     ` Vladimir Murzin

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=d4bb2979-4bc2-436c-8f4a-c9a5decea900@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=ashok.raj@oss.qualcomm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kirill@shutemov.name \
    --cc=liaochang1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --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