Re: [Qemu-devel] What TARGET_HAS_PRECISE_SMC means?

[Peter Maydell]

On 10 May 2012 12:29, 陳韋任 <address@hidden> wrote:
> From the backtrace I observed, the argument "is_cpu_write_access" is one only
> when guest is doing MMIO (see below).

It's one when the reason we got here is that the guest CPU did a write
instruction...

> ---
> #0  tb_invalidate_phys_page_range (start=229376, end=229380, 
> is_cpu_write_access=1) at /tmp/chenwj/qemu-0.13.0/exec.c:985
> #1  0x0000000000508bd2 in tb_invalidate_phys_page_fast (start=229376, len=4) 
> at /tmp/chenwj/qemu-0.13.0/exec.c:1112
> #2  0x000000000050c69b in notdirty_mem_writel (opaque=0x0, ram_addr=229376, 
> val=0) at /tmp/chenwj/qemu-0.13.0/exec.c:3120
> #3  0x000000000054e3c1 in io_writel (physaddr=229376, val=0, addr=229376, 
> retaddr=0x40016031) at /tmp/chenwj/qemu-0.13.0/softmmu_template.h:213
> #4  0x000000000054e4ab in __stl_mmu (addr=229376, val=0, mmu_idx=0) at 
> /tmp/chenwj/qemu-0.13.0/softmmu_template.h:245
> ---

...as we can see from your backtrace, which started off in __stl_mmu.

-- PMM