[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get c
From: |
malc |
Subject: |
Re: [Qemu-devel] Why we need unlink tb when cpu_interrupt/cpu_exit get called? |
Date: |
Mon, 2 Apr 2012 13:15:11 +0400 (MSK) |
User-agent: |
Alpine 2.00 (LNX 1167 2008-08-23) |
On Mon, 2 Apr 2012, ??? wrote:
> 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! :)
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
--
mailto:address@hidden