Re: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called?

[陳韋任]

> Try following with and without tb unlinking on aforementioned image to
> feel the difference:
> 
> sh-2.05b# echo "char main[]={0xeb,-2};" >h.c
> sh-2.05b# tcc -run h.c

  I think the example you gave me is an infinite loop, right? O.K., here is
what I got.

  Case 1. With tb unlinking
    - tcc runs infinitely and I can not stop it by using Ctrl + C. But I can use
      Ctrl + C to kill QEMU itself.

  Case 2. Without tb unlinking (I comment out the function body of 
cpu_unlink_tb)
    - tcc runs infinitely and without any responding. In case 1, the guest OS 
can
      respond to my keyboard. Besides, Ctrl + C can not terminate QEMU, I have 
to
      use `kill` to stop it.

Is this what you expect?

Regards,
chenwj

-- 
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj