Re: [PATCH] semihosting: Write back semihosting data before completion callback

2023-01-06 Thread Alex Bennée
Keith Packard writes: > 'lock_user' allocates a host buffer to shadow a target buffer, > 'unlock_user' copies that host buffer back to the target and frees the > host memory. If the completion function uses the target buffer, it > must be called after unlock_user to ensure the data are present.

Re: [PATCH] semihosting: Write back semihosting data before completion callback

2022-10-13 Thread Richard Henderson
On 10/12/22 18:48, Keith Packard via wrote: 'lock_user' allocates a host buffer to shadow a target buffer, 'unlock_user' copies that host buffer back to the target and frees the host memory. If the completion function uses the target buffer, it must be called after unlock_user to ensure the data

[PATCH] semihosting: Write back semihosting data before completion callback

2022-10-11 Thread Keith Packard via
'lock_user' allocates a host buffer to shadow a target buffer, 'unlock_user' copies that host buffer back to the target and frees the host memory. If the completion function uses the target buffer, it must be called after unlock_user to ensure the data are present. This caused the arm-compatible T