+16
−4
Loading
Since 0b57e287, cpu_memory_rw_debug already triggers a TB invalidation. As it doesn't (and cannot) set is_cpu_write_access=1 but "consumes" the currently executed TB, the tb_invalidate_phys_page_range call from patch_instruction didn't work anymore. Fix this by open-coding the required bits to restore the CPU state from the current TB position before patching and resume execution on the patched instruction afterward. Signed-off-by:Jan Kiszka <jan.kiszka@siemens.com> Tested-by:
Hervé Poussineau <hpoussin@reactos.org> Signed-off-by:
Blue Swirl <blauwirbel@gmail.com>