diff options
| author | Aurelien Jarno <aurelien@aurel32.net> | 2015-06-03 23:09:41 +0200 |
|---|---|---|
| committer | Alexander Graf <agraf@suse.de> | 2015-06-05 01:37:58 +0200 |
| commit | 111d7f4a69751d333bac32526cd252add6b071d3 (patch) | |
| tree | ed59dd7680c03dcd29905eba1dbad1a26cd4620f | |
| parent | a1c7610a68795d66249c25166220324d4d0b9289 (diff) | |
target-s390x: fix exception for invalid operation code
When an operation code is not recognized (ie invalid instruction) an
operation exception should be generated instead of a specification
exception. The latter is for valid opcode, with invalid operands or
modifiers.
This give a very basic GDB support in the guest, as it uses the invalid
opcode 0x0001 to generate a trap.
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Alexander Graf <agraf@suse.de>
| -rw-r--r-- | target-s390x/translate.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/target-s390x/translate.c b/target-s390x/translate.c index d508bc2b54..c7ebd21ec8 100644 --- a/target-s390x/translate.c +++ b/target-s390x/translate.c @@ -320,7 +320,7 @@ static void gen_program_exception(DisasContext *s, int code) static inline void gen_illegal_opcode(DisasContext *s) { - gen_program_exception(s, PGM_SPECIFICATION); + gen_program_exception(s, PGM_OPERATION); } #ifndef CONFIG_USER_ONLY |