On Tue, 12 Oct 2021 12:23:12 +0100, Marc Zyngier wrote: > We currently check SCTLR_EL1.EE when computing the address of > a faulting guest access. However, the fault could have occured at > EL0, in which case the right bit to check would be SCTLR_EL1.E0E. > > This is pretty unlikely to cause any issue in practice: You'd have > to have a guest with a LE EL1 and a BE EL0 (or the other way around), > and have mapped a device into the EL0 page tables. > > [...] Applied to next, thanks! [1/1] KVM: arm64: Fix reporting of endianess when the access originates at EL0 commit: 69adec18e94ff3ca20447916a3bd23ab1d06b878 Cheers, M. -- Without deviation from the norm, progress is not possible. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm