aboutsummaryrefslogtreecommitdiff
path: root/include/hw/nvram/xlnx-efuse.h
diff options
context:
space:
mode:
authorAlexander Graf <agraf@csgraf.de>2021-09-16 17:54:04 +0200
committerPeter Maydell <peter.maydell@linaro.org>2021-09-30 13:42:09 +0100
commit9fcd15b9193e819b6cc2fd0a45e3506148812bb4 (patch)
tree8f5eff6f23d858eeced9100b7035bae90cfe7454 /include/hw/nvram/xlnx-efuse.h
parent01e75d87834a5188f98defa2d1f88b69dca7e9a0 (diff)
downloadqemu-9fcd15b9193e819b6cc2fd0a45e3506148812bb4.zip
qemu-9fcd15b9193e819b6cc2fd0a45e3506148812bb4.tar.gz
qemu-9fcd15b9193e819b6cc2fd0a45e3506148812bb4.tar.bz2
arm: tcg: Adhere to SMCCC 1.3 section 5.2
The SMCCC 1.3 spec section 5.2 says The Unknown SMC Function Identifier is a sign-extended value of (-1) that is returned in the R0, W0 or X0 registers. An implementation must return this error code when it receives: * An SMC or HVC call with an unknown Function Identifier * An SMC or HVC call for a removed Function Identifier * An SMC64/HVC64 call from AArch32 state To comply with these statements, let's always return -1 when we encounter an unknown HVC or SMC call. Signed-off-by: Alexander Graf <agraf@csgraf.de> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'include/hw/nvram/xlnx-efuse.h')
0 files changed, 0 insertions, 0 deletions