Re: [PATCH v2] accel/tcg/user-exec: Fix read-modify-write of code on s390 hosts

2021-09-12 Thread Richard Henderson
On 8/3/21 3:16 PM, Ilya Leoshkevich wrote: x86_64 dotnet/runtime uses cmpxchg for code patching. When running it under s390x qemu-linux user, cpu_signal_handler() does not recognize this as a write and does not restore PAGE_WRITE cleared by tb_page_add(), incorrectly forwarding the signal to the

PING [PATCH v2] accel/tcg/user-exec: Fix read-modify-write of code on s390 hosts

2021-09-08 Thread Ilya Leoshkevich
On Wed, 2021-08-04 at 00:16 +0200, Ilya Leoshkevich wrote: > x86_64 dotnet/runtime uses cmpxchg for code patching. When running it > under s390x qemu-linux user, cpu_signal_handler() does not recognize > this as a write and does not restore PAGE_WRITE cleared by > tb_page_add(), incorrectly forward

Re: [PATCH v2] accel/tcg/user-exec: Fix read-modify-write of code on s390 hosts

2021-08-03 Thread Richard Henderson
On 8/3/21 12:16 PM, Ilya Leoshkevich wrote: x86_64 dotnet/runtime uses cmpxchg for code patching. When running it under s390x qemu-linux user, cpu_signal_handler() does not recognize this as a write and does not restore PAGE_WRITE cleared by tb_page_add(), incorrectly forwarding the signal to the

[PATCH v2] accel/tcg/user-exec: Fix read-modify-write of code on s390 hosts

2021-08-03 Thread Ilya Leoshkevich
x86_64 dotnet/runtime uses cmpxchg for code patching. When running it under s390x qemu-linux user, cpu_signal_handler() does not recognize this as a write and does not restore PAGE_WRITE cleared by tb_page_add(), incorrectly forwarding the signal to the guest code. Signed-off-by: Ilya Leoshkevich