Re: [RFC PATCH v8 06/23] target/arm: Add support for Non-maskable Interrupt

[Richard Henderson]

On 3/19/24 07:28, Peter Maydell wrote:
> >       switch (excp_idx) {
> > +    case EXCP_NMI:
> > +        pstate_unmasked = !allIntMask;
> > +        break;
> > +
> > +    case EXCP_VNMI:
> > +        if ((!(hcr_el2 & HCR_IMO) && !(hcr_el2 & HCR_FMO)) ||
> > +             (hcr_el2 & HCR_TGE)) {
> > +            /* VNMIs(VIRQs or VFIQs) are only taken when hypervized.  */
> > +            return false;
> > +        }
>
> VINMI and VFNMI aren't the same thing: do we definitely want to
> merge them into one EXCP_VNMI ?

We do not, which is why VFNMI is going through EXCP_VFIQ.  A previous version did, and I 
see the comment did not change to match the new implementation.

> The use of the _eff() versions of the functions here is
> correct but it introduces a new case where we need to
> reevaluate the status of the VNMI etc interrupt status:
> when we change from Secure to NonSecure or when we change
> SCR_EL3.EEL2 or SCR_EL3.HXEN. We either need to make sure
> we reevaluate when we drop from EL3 to EL2 (which would be
> OK since VINMI and VFNMI can't be taken at EL3 and none of
> these bits can change except at EL3) or else make the calls
> to reevaluate them when we write to SCR_EL3. At least, I don't
> think we currently reevaluate these bits on an EL change.

We re-evaluate these bits on EL change via gicv3_cpuif_el_change_hook.


r~