summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_missing/host_missing/accel_TCG/1856
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_TCG/1856')
-rw-r--r--gitlab/issues_text/target_missing/host_missing/accel_TCG/185613
1 files changed, 13 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_TCG/1856 b/gitlab/issues_text/target_missing/host_missing/accel_TCG/1856
new file mode 100644
index 000000000..6d02df80b
--- /dev/null
+++ b/gitlab/issues_text/target_missing/host_missing/accel_TCG/1856
@@ -0,0 +1,13 @@
+Replay got stuck with consecutive hardware interrupts coming
+Description of problem:
+I recorded bin file using **_rr=record_** command line. But it got stuck when replaying this record bin file. The icount number would never change after stucking if I typed _**info replay**_ with qmp command line.
+
+I found that the following instructions should be a sequence of consecutive hardware interrupts after stucking once checking the trace log of 
+both replay and record log using _**-d in_asm,int**_.
+Steps to reproduce:
+1.pulling from remote which the newest commit ID is 156618d9ea67f2f2e31d9dedd97f2dcccbe6808c
+2.emulating  Windows 7 OS on aarch64 Host with TCG acceleration mechanism
+3.using **_rr=record_** to make replay file and tracing guest code and interrupts using _**-d in_asm,int**_
+4.replaying the previous file and also tracing guest code and interrupts
+Additional information:
+#