All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinjie Ruan via <qemu-devel@nongnu.org>
To: <peter.maydell@linaro.org>, <eduardo@habkost.net>,
	<marcel.apfelbaum@gmail.com>, <philmd@linaro.org>,
	<wangyanan55@huawei.com>, <qemu-devel@nongnu.org>,
	<qemu-arm@nongnu.org>
Cc: <ruanjinjie@huawei.com>
Subject: [RFC PATCH v4 08/22] target/arm: Handle IS/FS in ISR_EL1 for NMI
Date: Wed, 28 Feb 2024 09:29:32 +0000	[thread overview]
Message-ID: <20240228092946.1768728-9-ruanjinjie@huawei.com> (raw)
In-Reply-To: <20240228092946.1768728-1-ruanjinjie@huawei.com>

Add IS and FS bit in ISR_EL1 and handle the read. With CPU_INTERRUPT_NMI or
CPU_INTERRUPT_VNMI, both CPSR_I and ISR_IS must be set. With
CPU_INTERRUPT_VFIQ and HCRX_EL2.VFNMI set, both CPSR_F and ISR_FS must be set.

Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
---
v4;
- Also handle VNMI.
v3:
- CPU_INTERRUPT_NMI do not set FIQ, so remove it.
- With CPU_INTERRUPT_NMI, both CPSR_I and ISR_IS must be set.
---
 target/arm/cpu.h    |  2 ++
 target/arm/helper.c | 13 +++++++++++++
 2 files changed, 15 insertions(+)

diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 8be978698d..22f0763e66 100644
--- a/target/arm/cpu.h
+++ b/target/arm/cpu.h
@@ -1475,6 +1475,8 @@ FIELD(CPTR_EL3, TCPAC, 31, 1)
 #define CPSR_N (1U << 31)
 #define CPSR_NZCV (CPSR_N | CPSR_Z | CPSR_C | CPSR_V)
 #define CPSR_AIF (CPSR_A | CPSR_I | CPSR_F)
+#define ISR_FS (1U << 9)
+#define ISR_IS (1U << 10)
 
 #define CPSR_IT (CPSR_IT_0_1 | CPSR_IT_2_7)
 #define CACHED_CPSR_BITS (CPSR_T | CPSR_AIF | CPSR_GE | CPSR_IT | CPSR_Q \
diff --git a/target/arm/helper.c b/target/arm/helper.c
index 7cdc90e9e3..ac44498537 100644
--- a/target/arm/helper.c
+++ b/target/arm/helper.c
@@ -2018,15 +2018,28 @@ static uint64_t isr_read(CPUARMState *env, const ARMCPRegInfo *ri)
         if (cs->interrupt_request & CPU_INTERRUPT_VIRQ) {
             ret |= CPSR_I;
         }
+        if (cs->interrupt_request & CPU_INTERRUPT_VNMI) {
+            ret |= ISR_IS;
+            ret |= CPSR_I;
+        }
     } else {
         if (cs->interrupt_request & CPU_INTERRUPT_HARD) {
             ret |= CPSR_I;
         }
+
+        if (cs->interrupt_request & CPU_INTERRUPT_NMI) {
+            ret |= ISR_IS;
+            ret |= CPSR_I;
+        }
     }
 
     if (hcr_el2 & HCR_FMO) {
         if (cs->interrupt_request & CPU_INTERRUPT_VFIQ) {
             ret |= CPSR_F;
+
+            if (env->cp15.hcrx_el2 & HCRX_VFNMI) {
+                ret |= ISR_FS;
+            }
         }
     } else {
         if (cs->interrupt_request & CPU_INTERRUPT_FIQ) {
-- 
2.34.1



  parent reply	other threads:[~2024-02-28  9:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  9:29 [RFC PATCH v4 00/22] target/arm: Implement FEAT_NMI and FEAT_GICv3_NMI Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 01/22] target/arm: Handle HCR_EL2 accesses for bits introduced with FEAT_NMI Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 02/22] target/arm: Add PSTATE.ALLINT Jinjie Ruan via
2024-02-28 20:37   ` Richard Henderson
2024-02-28  9:29 ` [RFC PATCH v4 03/22] target/arm: Add support for FEAT_NMI, Non-maskable Interrupt Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 04/22] target/arm: Implement ALLINT MSR (immediate) Jinjie Ruan via
2024-02-28 20:46   ` Richard Henderson
2024-02-28  9:29 ` [RFC PATCH v4 05/22] target/arm: Support MSR access to ALLINT Jinjie Ruan via
2024-02-28 20:46   ` Richard Henderson
2024-02-28  9:29 ` [RFC PATCH v4 06/22] target/arm: Add support for Non-maskable Interrupt Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 07/22] target/arm: Add support for NMI in arm_phys_excp_target_el() Jinjie Ruan via
2024-02-28  9:29 ` Jinjie Ruan via [this message]
2024-02-28  9:29 ` [RFC PATCH v4 09/22] target/arm: Handle PSTATE.ALLINT on taking an exception Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 10/22] hw/arm/virt: Wire NMI and VNMI irq lines from GIC to CPU Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 11/22] hw/intc/arm_gicv3: Add external IRQ lines for NMI Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 12/22] target/arm: Handle NMI in arm_cpu_do_interrupt_aarch64() Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 13/22] hw/intc/arm_gicv3: Add irq superpriority information Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 14/22] hw/intc/arm_gicv3_redist: Implement GICR_INMIR0 Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 15/22] hw/intc/arm_gicv3: Implement GICD_INMIR Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 16/22] hw/intc: Enable FEAT_GICv3_NMI Feature Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 17/22] hw/intc/arm_gicv3: Add NMI handling CPU interface registers Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 18/22] hw/intc/arm_gicv3: Implement NMI interrupt prioirty Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 19/22] hw/intc/arm_gicv3: Report the NMI interrupt in gicv3_cpuif_update() Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 20/22] hw/intc/arm_gicv3: Report the VNMI interrupt Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 21/22] target/arm: Add FEAT_NMI to max Jinjie Ruan via
2024-02-28  9:29 ` [RFC PATCH v4 22/22] hw/arm/virt: Add FEAT_GICv3_NMI feature support in virt GIC Jinjie Ruan via

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=20240228092946.1768728-9-ruanjinjie@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=eduardo@habkost.net \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=ruanjinjie@huawei.com \
    --cc=wangyanan55@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.