diff options
author | Markus Armbruster <armbru@redhat.com> | 2019-03-08 10:45:57 +0100 |
---|---|---|
committer | Markus Armbruster <armbru@redhat.com> | 2019-03-11 22:53:44 +0100 |
commit | 2d93bebf81520ccebeb9a3ea9bd051ce088854ea (patch) | |
tree | 84bd943d5dc3fcdbf8ffb3bda8ed98d10c18a28a /tests/qemu-iotests/220 | |
parent | 1643406520f8ff6f4cc11062950f5f898b03b573 (diff) | |
download | qemu-2d93bebf81520ccebeb9a3ea9bd051ce088854ea.zip qemu-2d93bebf81520ccebeb9a3ea9bd051ce088854ea.tar.gz qemu-2d93bebf81520ccebeb9a3ea9bd051ce088854ea.tar.bz2 |
pflash_cfi01: Do not exit() on guest aborting "write to buffer"
When a guest tries to abort "write to buffer" (command 0xE8), we print
"PFLASH: Possible BUG - Write block confirm", then exit(1). Letting
the guest terminate QEMU is not a good idea. Instead, LOG_UNIMP we
screwed up, then reset the device.
Macro PFLASH_BUG() is now unused; delete it.
Suggested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20190308094610.21210-3-armbru@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/220')
0 files changed, 0 insertions, 0 deletions