Jan Kiszka a écrit :
> From: Jan Kiszka <jan.kis...@siemens.com>
>
> 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.kis...@siemens.com>
> ---
>
Tested-by: Hervé Poussineau <hpous...@reactos.org>
However, I had to initialize current_pc, current_cs_base and
current_flags to 0 to prevent uninitialized warning.
(GCC 4.7.1, KVM disabled by configure)
Regards,
Hervé
