From: Gavin Shan <gshan@redhat.com>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, drjones@redhat.com,
jthierry@redhat.com, aik@ozlabs.ru, maz@kernel.org,
eric.auger@redhat.com, shan.gavin@gmail.com, pbonzini@redhat.com
Subject: Re: [RESEND RFC PATCH v2 1/2] target/arm: Allow to inject SError interrupt
Date: Wed, 12 Feb 2020 17:39:31 +1100 [thread overview]
Message-ID: <8dce7dbe-c6c1-122a-f960-0fc29257dd1c@redhat.com> (raw)
In-Reply-To: <20200205110541.37811-2-gshan@redhat.com>
On 2/5/20 10:05 PM, Gavin Shan wrote:
> This allows to inject SError interrupt, which will be used on receiving
> QMP/HMP "nmi" command in next patch.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> target/arm/cpu.c | 11 +++++++++++
> target/arm/cpu.h | 12 +++++++++---
> target/arm/helper.c | 4 ++++
> 3 files changed, 24 insertions(+), 3 deletions(-)
>
Hi Peter, could you please take a look when you get a chance? I'm not sure
the implementation is good enough to inject SError. If there are somebody
else who can help to review, please let me know so that I can copy her/him
either.
Thanks,
Gavin
> diff --git a/target/arm/cpu.c b/target/arm/cpu.c
> index f86e71a260..24fd77437b 100644
> --- a/target/arm/cpu.c
> +++ b/target/arm/cpu.c
> @@ -461,6 +461,17 @@ bool arm_cpu_exec_interrupt(CPUState *cs, int interrupt_request)
> }
> }
>
> + if (interrupt_request & CPU_INTERRUPT_SERROR) {
> + excp_idx = EXCP_SERROR;
> + target_el = arm_phys_excp_target_el(cs, excp_idx, cur_el, secure);
> + if (arm_excp_unmasked(cs, excp_idx, target_el)) {
> + cs->exception_index = excp_idx;
> + env->exception.target_el = target_el;
> + cc->do_interrupt(cs);
> + ret = true;
> + }
> + }
> +
> return ret;
> }
>
> diff --git a/target/arm/cpu.h b/target/arm/cpu.h
> index 608fcbd0b7..0bbc46ff6d 100644
> --- a/target/arm/cpu.h
> +++ b/target/arm/cpu.h
> @@ -49,6 +49,7 @@
> #define EXCP_LAZYFP 20 /* v7M fault during lazy FP stacking */
> #define EXCP_LSERR 21 /* v8M LSERR SecureFault */
> #define EXCP_UNALIGNED 22 /* v7M UNALIGNED UsageFault */
> +#define EXCP_SERROR 23 /* SError Interrupt */
> /* NB: add new EXCP_ defines to the array in arm_log_exception() too */
>
> #define ARMV7M_EXCP_RESET 1
> @@ -79,9 +80,10 @@ enum {
> };
>
> /* ARM-specific interrupt pending bits. */
> -#define CPU_INTERRUPT_FIQ CPU_INTERRUPT_TGT_EXT_1
> -#define CPU_INTERRUPT_VIRQ CPU_INTERRUPT_TGT_EXT_2
> -#define CPU_INTERRUPT_VFIQ CPU_INTERRUPT_TGT_EXT_3
> +#define CPU_INTERRUPT_FIQ CPU_INTERRUPT_TGT_EXT_1
> +#define CPU_INTERRUPT_VIRQ CPU_INTERRUPT_TGT_EXT_2
> +#define CPU_INTERRUPT_VFIQ CPU_INTERRUPT_TGT_EXT_3
> +#define CPU_INTERRUPT_SERROR CPU_INTERRUPT_TGT_EXT_4
>
> /* The usual mapping for an AArch64 system register to its AArch32
> * counterpart is for the 32 bit world to have access to the lower
> @@ -2731,6 +2733,10 @@ static inline bool arm_excp_unmasked(CPUState *cs, unsigned int excp_idx,
> pstate_unmasked = !(env->daif & PSTATE_I);
> break;
>
> + case EXCP_SERROR:
> + pstate_unmasked = !(env->daif & PSTATE_A);
> + break;
> +
> case EXCP_VFIQ:
> if (secure || !(hcr_el2 & HCR_FMO) || (hcr_el2 & HCR_TGE)) {
> /* VFIQs are only taken when hypervized and non-secure. */
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index 19a57a17da..622a1d8796 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -7980,6 +7980,7 @@ void arm_log_exception(int idx)
> [EXCP_LAZYFP] = "v7M exception during lazy FP stacking",
> [EXCP_LSERR] = "v8M LSERR UsageFault",
> [EXCP_UNALIGNED] = "v7M UNALIGNED UsageFault",
> + [EXCP_SERROR] = "SError Interrupt",
> };
>
> if (idx >= 0 && idx < ARRAY_SIZE(excnames)) {
> @@ -8566,6 +8567,9 @@ static void arm_cpu_do_interrupt_aarch64(CPUState *cs)
> case EXCP_VFIQ:
> addr += 0x100;
> break;
> + case EXCP_SERROR:
> + addr += 0x180;
> + break;
> default:
> cpu_abort(cs, "Unhandled exception 0x%x\n", cs->exception_index);
> }
>
next prev parent reply other threads:[~2020-02-12 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:05 [RESEND RFC PATCH v2 1/2] target/arm: Allow to inject SError interrupt Gavin Shan
2020-02-12 6:39 ` Gavin Shan [this message]
2020-02-12 11:34 ` Peter Maydell
2020-02-13 3:49 ` Gavin Shan
2020-02-13 5:39 ` Richard Henderson
2020-02-13 11:09 ` Gavin Shan
2020-02-13 10:31 ` Peter Maydell
2020-02-14 2:25 ` Gavin Shan
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=8dce7dbe-c6c1-122a-f960-0fc29257dd1c@redhat.com \
--to=gshan@redhat.com \
--cc=aik@ozlabs.ru \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jthierry@redhat.com \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shan.gavin@gmail.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 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).