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

[malc]

On Mon, 2 Apr 2012, ??? wrote:

> > 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.

Yes, it's "0: jmp 0b"

> 
>   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.

You can also interactw with monitor and whatnot, IOW I/O loops is
running, IEYOW QEMU is not 100% occupied with running the guest code,
since it can unlink the TB and do other work.

> 
>   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?

Yes.

-- 
mailto:address@hidden