From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called?
Date: Mon, 2 Apr 2012 11:45:42 +0800 [thread overview]
Message-ID: <20120402034542.GA59901@cs.nctu.edu.tw> (raw)
Hi all,
I am wondering why we need to unlink tb when cpu_interrupt/cpu_exit is
called, and want to know what happened if we don't unlink tb. In theory,
QEMU want the execution flow comes back from code cache to QEMU itself
so that interrupts can be handled as soon as possible. However, I ran
linux-0.2.img with a modified QEMU whose cpu_unlink_tb does nothing.
Everything seems work fine. Is this experiment too trivial to show what
bad things happened when we don't unlink tb?
Thanks! :)
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
next reply other threads:[~2012-04-02 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 3:45 陳韋任 [this message]
2012-04-02 9:15 ` [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called? malc
2012-04-02 10:21 ` 陳韋任
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=20120402034542.GA59901@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--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).