diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2022-04-08 15:15:19 +0100 |
---|---|---|
committer | Peter Maydell <peter.maydell@linaro.org> | 2022-04-22 09:24:43 +0100 |
commit | 93f4fdcd4d98c0de8e056e08016bce7d71a91100 (patch) | |
tree | 2e1dbce5463b6ccab566b2296f3a29c78a4f38f3 /tests/qapi-schema/nested-struct-data.err | |
parent | 0cdf7a5dc8d4e49b19d91219dc3e3cc65d6d8c60 (diff) | |
download | qemu-93f4fdcd4d98c0de8e056e08016bce7d71a91100.zip qemu-93f4fdcd4d98c0de8e056e08016bce7d71a91100.tar.gz qemu-93f4fdcd4d98c0de8e056e08016bce7d71a91100.tar.bz2 |
hw/intc/arm_gicv3_its: Distinguish success and error cases of CMD_CONTINUE
In the ItsCmdResult enum, we currently distinguish only CMD_STALL
(failure, stall processing of the command queue) and CMD_CONTINUE
(keep processing the queue), and we use the latter both for "there
was a parameter error, go on to the next command" and "the command
succeeded, go on to the next command". Sometimes we would like to
distinguish those two cases, so add CMD_CONTINUE_OK to the enum to
represent the success situation, and use it in the relevant places.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-id: 20220408141550.1271295-11-peter.maydell@linaro.org
Diffstat (limited to 'tests/qapi-schema/nested-struct-data.err')
0 files changed, 0 insertions, 0 deletions