kernel: 0.977
device: 0.973
socket: 0.949
virtual: 0.948
debug: 0.944
files: 0.943
permissions: 0.918
graphic: 0.914
peripherals: 0.913
risc-v: 0.906
boot: 0.901
user-level: 0.875
network: 0.868
performance: 0.854
vnc: 0.818
PID: 0.800
register: 0.757
semantic: 0.708
arm: 0.649
ppc: 0.644
architecture: 0.628
VMM: 0.597
mistranslation: 0.594
x86: 0.525
hypervisor: 0.406
TCG: 0.358
assembly: 0.220
KVM: 0.196
i386: 0.132

qemu-system-riscv64 can't break by gdb
Description of problem:
The qemu-system-riscv64 can't break by gdb.  
( => The target is not responding to interrupt requests.  
Stop debugging it? (y or n) Quit)  

I using old qemu-system-risc64(7.2) don't has this issue.  

This test case running simple OS(riscv-xv6).
Steps to reproduce:
1.qemu-system-riscv64 -machine virt -bios none -kernel kernel/kernel -m 128M -smp 3 -nographic -global   virtio-mmio.force-legacy=false -drive file=fs.img,if=none,format=raw,id=x0 -device virtio-blk-  device,drive=x0,bus=virtio-mmio-bus.0 -S -gdb tcp::26000  
  
  
2.test@test-VirtualBox:~$ riscv64-unknown-linux-gnu-gdb -q                                                                                                                                                 
(gdb) target remote :26000  
Remote debugging using :26000  
warning: No executable has been specified and target does not support  
determining executable automatically.  Try using the "file" command.  
0x0000000000001000 in ?? ()  
(gdb) c  
Continuing.  

3.check xv6 is running.  
xv6 kernel is booting  

hart 2 starting  
hart 1 starting  
init: starting sh  
$  

4.Can't stop by GDB.  
(gdb) c  
Continuing.  
^C^CThe target is not responding to interrupt requests.  
Stop debugging it? (y or n) Quit  
(gdb)
Additional information:
Test on new QEMU.  

```
commit cab35c73be9d579db105ef73fa8a60728a890098 (HEAD -> master, origin/staging, origin/master, origin/HEAD)
Merge: 48ab886d3d d7ee93e243
Author: Richard Henderson <richard.henderson@linaro.org>
Date:   Tue Jun 20 10:26:53 2023 +0200
```