qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, 陳韋任 <chenwj@iis.sinica.edu.tw>
Subject: Re: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called?
Date: Mon, 2 Apr 2012 18:21:23 +0800	[thread overview]
Message-ID: <20120402102123.GA81576@cs.nctu.edu.tw> (raw)
In-Reply-To: <alpine.LNX.2.00.1204021255300.9502@linmac>

> 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

  reply	other threads:[~2012-04-02 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02  3:45 [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called? 陳韋任
2012-04-02  9:15 ` malc
2012-04-02 10:21   ` 陳韋任 [this message]
2012-04-02 10:32     ` malc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120402102123.GA81576@cs.nctu.edu.tw \
    --to=chenwj@iis.sinica.edu.tw \
    --cc=av1474@comtv.ru \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).