Kaynağa Gözat

docs/emulation: expand warning about semihosting

A surprising feature of calls like SYS_READC is this can cause QEMU to
indefinitely block as there is no handling for EOF.

Clarifies: https://gitlab.com/qemu-project/qemu/-/issues/1963
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20231120150833.2552739-8-alex.bennee@linaro.org>
Alex Bennée 1 yıl önce
ebeveyn
işleme
ef073ebd32
1 değiştirilmiş dosya ile 3 ekleme ve 2 silme
  1. 3 2
      docs/about/emulation.rst

+ 3 - 2
docs/about/emulation.rst

@@ -129,8 +129,9 @@ causing most hypervisors to trap and fault on them.
 .. warning::
 .. warning::
    Semihosting inherently bypasses any isolation there may be between
    Semihosting inherently bypasses any isolation there may be between
    the guest and the host. As a result a program using semihosting can
    the guest and the host. As a result a program using semihosting can
-   happily trash your host system. You should only ever run trusted
-   code with semihosting enabled.
+   happily trash your host system. Some semihosting calls (e.g.
+   ``SYS_READC``) can block execution indefinitely. You should only
+   ever run trusted code with semihosting enabled.
 
 
 Redirection
 Redirection
 ~~~~~~~~~~~
 ~~~~~~~~~~~