Revert "arm: tcg: Adhere to SMCCC 1.3 section 5.2"
This reverts commit 9fcd15b919
.
This change turns out to cause regressions, for instance on the
imx6ul boards as described here:
https://lore.kernel.org/qemu-devel/c8b89685-7490-328b-51a3-48711c140a84@tribudubois.net/
The primary cause of that regression is that the guest code running
at EL3 expects SMCs (not related to PSCI) to do what they would if
our PSCI emulation was not present at all, but after this change
they instead set a value in R0/X0 and continue.
We could fix that by a refactoring that allowed us to only turn on
the PSCI emulation if we weren't booting the guest at EL3, but there
is a more tangled problem with the highbank board, which:
(1) wants to enable PSCI emulation
(2) has a bit of guest code that it wants to run at EL3 and
to perform SMC calls that trap to the monitor vector table:
this is the boot stub code that is written to memory by
arm_write_secure_board_setup_dummy_smc() and which the
highbank board enables by setting bootinfo->secure_board_setup
We can't satisfy both of those and also have the PSCI emulation
handle all SMC instruction executions regardless of function
identifier value.
This is too tricky to try to sort out before 6.2 is released;
revert this commit so we can take the time to get it right in
the 7.0 release.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Message-id: 20211119163419.557623-1-peter.maydell@linaro.org
This commit is contained in:
parent
49aaac3548
commit
4825eaae4f
@ -27,13 +27,15 @@
|
||||
|
||||
bool arm_is_psci_call(ARMCPU *cpu, int excp_type)
|
||||
{
|
||||
/*
|
||||
* Return true if the exception type matches the configured PSCI conduit.
|
||||
* This is called before the SMC/HVC instruction is executed, to decide
|
||||
* whether we should treat it as a PSCI call or with the architecturally
|
||||
/* Return true if the r0/x0 value indicates a PSCI call and
|
||||
* the exception type matches the configured PSCI conduit. This is
|
||||
* called before the SMC/HVC instruction is executed, to decide whether
|
||||
* we should treat it as a PSCI call or with the architecturally
|
||||
* defined behaviour for an SMC or HVC (which might be UNDEF or trap
|
||||
* to EL2 or to EL3).
|
||||
*/
|
||||
CPUARMState *env = &cpu->env;
|
||||
uint64_t param = is_a64(env) ? env->xregs[0] : env->regs[0];
|
||||
|
||||
switch (excp_type) {
|
||||
case EXCP_HVC:
|
||||
@ -50,7 +52,27 @@ bool arm_is_psci_call(ARMCPU *cpu, int excp_type)
|
||||
return false;
|
||||
}
|
||||
|
||||
return true;
|
||||
switch (param) {
|
||||
case QEMU_PSCI_0_2_FN_PSCI_VERSION:
|
||||
case QEMU_PSCI_0_2_FN_MIGRATE_INFO_TYPE:
|
||||
case QEMU_PSCI_0_2_FN_AFFINITY_INFO:
|
||||
case QEMU_PSCI_0_2_FN64_AFFINITY_INFO:
|
||||
case QEMU_PSCI_0_2_FN_SYSTEM_RESET:
|
||||
case QEMU_PSCI_0_2_FN_SYSTEM_OFF:
|
||||
case QEMU_PSCI_0_1_FN_CPU_ON:
|
||||
case QEMU_PSCI_0_2_FN_CPU_ON:
|
||||
case QEMU_PSCI_0_2_FN64_CPU_ON:
|
||||
case QEMU_PSCI_0_1_FN_CPU_OFF:
|
||||
case QEMU_PSCI_0_2_FN_CPU_OFF:
|
||||
case QEMU_PSCI_0_1_FN_CPU_SUSPEND:
|
||||
case QEMU_PSCI_0_2_FN_CPU_SUSPEND:
|
||||
case QEMU_PSCI_0_2_FN64_CPU_SUSPEND:
|
||||
case QEMU_PSCI_0_1_FN_MIGRATE:
|
||||
case QEMU_PSCI_0_2_FN_MIGRATE:
|
||||
return true;
|
||||
default:
|
||||
return false;
|
||||
}
|
||||
}
|
||||
|
||||
void arm_handle_psci_call(ARMCPU *cpu)
|
||||
@ -172,9 +194,10 @@ void arm_handle_psci_call(ARMCPU *cpu)
|
||||
break;
|
||||
case QEMU_PSCI_0_1_FN_MIGRATE:
|
||||
case QEMU_PSCI_0_2_FN_MIGRATE:
|
||||
default:
|
||||
ret = QEMU_PSCI_RET_NOT_SUPPORTED;
|
||||
break;
|
||||
default:
|
||||
g_assert_not_reached();
|
||||
}
|
||||
|
||||
err:
|
||||
|
Loading…
Reference in New Issue
Block a user