Peter Maydell 45704e8904 semihosting: Don't copy buffer after console_write() ... The console_write() semihosting function outputs guest data from a buffer; it doesn't update that buffer. It therefore doesn't need to pass a length value to unlock_user(), but can pass 0, meaning "do not copy any data back to the guest memory". Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-Id: <20220719121110.225657-3-peter.maydell@linaro.org> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20220725140520.515340-8-alex.bennee@linaro.org>		2022-07-29 09:48:01 +01:00
..
arm-compat-semi.c	semihosting: Use console_out_gf for SYS_WRITE0	2022-06-28 04:40:47 +05:30
config.c	semihosting: Cleanup chardev init	2022-06-28 04:35:52 +05:30
console.c	semihosting: Don't return negative values on qemu_semihosting_console_write() failure	2022-07-29 09:48:01 +01:00
guestfd.c	semihosting: Create qemu_semihosting_guestfd_init	2022-06-28 04:36:50 +05:30
Kconfig
meson.build	semihosting: Split out semihost_sys_open	2022-06-28 04:35:39 +05:30
syscalls.c	semihosting: Don't copy buffer after console_write()	2022-07-29 09:48:01 +01:00
uaccess.c	semihosting: Simplify softmmu_lock_user_string	2022-06-28 04:35:06 +05:30