aboutsummaryrefslogtreecommitdiff
path: root/hw/intc/sh_intc.c
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2024-03-14 17:58:25 +0100
committerKevin Wolf <kwolf@redhat.com>2024-03-18 13:12:51 +0100
commite8fce34eccf68a32f4ecf2c6f121ff2ac383d6bf (patch)
tree224322c2d9628cbeef9e065dd6793d1f80cfefd3 /hw/intc/sh_intc.c
parent9c707525cbb1dd1e56876e45c70c0c08f2876d41 (diff)
downloadqemu-e8fce34eccf68a32f4ecf2c6f121ff2ac383d6bf.zip
qemu-e8fce34eccf68a32f4ecf2c6f121ff2ac383d6bf.tar.gz
qemu-e8fce34eccf68a32f4ecf2c6f121ff2ac383d6bf.tar.bz2
iotests: Add test for reset/AioContext switches with NBD exports
This replicates the scenario in which the bug was reported. Unfortunately this relies on actually executing a guest (so that the firmware initialises the virtio-blk device and moves it to its configured iothread), so this can't make use of the qtest accelerator like most other test cases. I tried to find a different easy way to trigger the bug, but couldn't find one. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20240314165825.40261-3-kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/intc/sh_intc.c')
0 files changed, 0 insertions, 0 deletions