[PATCH 1/7] target/ppc: Fix CPU reservation migration for record-replay

2023-07-26 Thread Nicholas Piggin
ppc only migrates reserve_addr, so the destination machine can get a valid reservation with an incorrect reservation value of 0. Prior to commit 392d328abe753 ("target/ppc: Ensure stcx size matches larx"), this could permit a stcx. to incorrectly succeed. That commit inadvertently fixed that bug

Re: [PATCH 1/7] target/ppc: Fix CPU reservation migration for record-replay

2023-07-07 Thread Daniel Henrique Barboza
Nick, On 6/23/23 09:57, Nicholas Piggin wrote: ppc only migrates reserve_addr, so the destination machine can get a valid reservation with an incorrect reservation value of 0. Prior to commit 392d328abe753 ("target/ppc: Ensure stcx size matches larx"), this could permit a stcx. to incorrectly

Re: [PATCH 1/7] target/ppc: Fix CPU reservation migration for record-replay

2023-06-26 Thread Pavel Dovgalyuk
Acked-by: Pavel Dovgalyuk On 23.06.2023 15:57, Nicholas Piggin wrote: ppc only migrates reserve_addr, so the destination machine can get a valid reservation with an incorrect reservation value of 0. Prior to commit 392d328abe753 ("target/ppc: Ensure stcx size matches larx"), this could permit

[PATCH 1/7] target/ppc: Fix CPU reservation migration for record-replay

2023-06-23 Thread Nicholas Piggin
ppc only migrates reserve_addr, so the destination machine can get a valid reservation with an incorrect reservation value of 0. Prior to commit 392d328abe753 ("target/ppc: Ensure stcx size matches larx"), this could permit a stcx. to incorrectly succeed. That commit inadvertently fixed that bug