[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC v2 0/5] Move notdirty handling to cputlb
|
From: |
Richard Henderson |
|
Subject: |
Re: [RFC v2 0/5] Move notdirty handling to cputlb |
|
Date: |
Sat, 21 Sep 2019 15:21:59 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 9/18/19 11:02 AM, Richard Henderson wrote:
> However this time the changes are extremely minimal, and now
> I really *really* don't understand why they don't work, because
> as far as I can tell the new locking is *identical* with the
> current i/o path.
The difference was failing to set cpu->mem_io_pc, so that
TARGET_HAS_PRECISE_SMC within tb_invalidate_phys_page_range__locked could look
up the current TB, and potentially restore state and exit to the main loop.
Version 3 will have this fixed.
r~
- Re: [RFC v2 2/5] cputlb: Replace switches in load/store_helper with callback, (continued)
- [Qemu-devel] [RFC v2 4/5] exec: Adjust notdirty tracing, Richard Henderson, 2019/09/18
- [Qemu-devel] [RFC v2 5/5] cputlb: Move NOTDIRTY handling from I/O path to TLB path, Richard Henderson, 2019/09/18
- [Qemu-devel] [RFC v2 3/5] cputlb: Introduce TLB_BSWAP, Richard Henderson, 2019/09/18
- Re: [Qemu-devel] [RFC v2 0/5] Move notdirty handling to cputlb, no-reply, 2019/09/19
- Re: [Qemu-devel] [RFC v2 0/5] Move notdirty handling to cputlb, no-reply, 2019/09/19
- Re: [Qemu-devel] [RFC v2 0/5] Move notdirty handling to cputlb, no-reply, 2019/09/19
- Re: [RFC v2 0/5] Move notdirty handling to cputlb,
Richard Henderson <=