From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:50398)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1SEeOP-0005mW-4z
	for qemu-devel@nongnu.org; Mon, 02 Apr 2012 06:21:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1SEeOI-0005Jb-TQ
	for qemu-devel@nongnu.org; Mon, 02 Apr 2012 06:21:44 -0400
Received: from csmailer.cs.nctu.edu.tw ([140.113.235.130]:44958)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1SEeOI-0005JE-7Z
	for qemu-devel@nongnu.org; Mon, 02 Apr 2012 06:21:38 -0400
Date: Mon, 2 Apr 2012 18:21:23 +0800
From: =?utf-8?B?6Zmz6Z+L5Lu7?= <chenwj@iis.sinica.edu.tw>
Message-ID: <20120402102123.GA81576@cs.nctu.edu.tw>
References: <20120402034542.GA59901@cs.nctu.edu.tw>
	<alpine.LNX.2.00.1204021255300.9502@linmac>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <alpine.LNX.2.00.1204021255300.9502@linmac>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit
 get called?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, =?utf-8?B?6Zmz6Z+L5Lu7?= <chenwj@iis.sinica.edu.tw>

> Try following with and without tb unlinking on aforementioned image to
> feel the difference:
>=20
> sh-2.05b# echo "char main[]=3D{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_un=
link_tb)
    - tcc runs infinitely and without any responding. In case 1, the gues=
t 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

--=20
Wei-Ren Chen (=E9=99=B3=E9=9F=8B=E4=BB=BB)
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