aboutsummaryrefslogtreecommitdiff
path: root/board-qemu/slof/virtio-serial.fs
diff options
context:
space:
mode:
authorGreg Kurz <groug@kaod.org>2020-03-26 11:32:43 +0100
committerAlexey Kardashevskiy <aik@ozlabs.ru>2020-03-27 11:55:00 +1100
commit76fee95890f7a80665a7cdb5eff73d064c141453 (patch)
tree8f13f44d059257470f6a7e783ea74b66c330e926 /board-qemu/slof/virtio-serial.fs
parentab6984f5a6d054e1f634dda855b32e5357111974 (diff)
downloadSLOF-76fee95890f7a80665a7cdb5eff73d064c141453.zip
SLOF-76fee95890f7a80665a7cdb5eff73d064c141453.tar.gz
SLOF-76fee95890f7a80665a7cdb5eff73d064c141453.tar.bz2
slof: Only close stdout for virtio-serial devices
Recent commit cf28264196e5 fixed an issue where a virtio-serial device wouldn't shutdown properly during quiesce. The fix is to close stdout just before quiesce. As expected this causes some messages to not appear anymore, like the well known ones from prom_init(): Quiescing Open Firmware ... Booting Linux via __start() @ 0x0000000002000000 ... Actually all messages are discarded until the OS driver finally takes control of the device, which may represent a fair amount of logging. This is suboptimal but this still better than hanging in SLOF. The hammer is a bit too big though because the change also affects spapr-vty based consoles, which have no reason to stop working after quiesce. Move the hack from the common code to the virtio-serial code so that it doesn't affect other device types anymore. Register a quiesce hook that closes stdout in virtio-serial.fs. While here, as suggested by Segher, bring back some robustness in the shutdown method. Reported-by: Fabiano Rosas <farosas@linux.ibm.com> Fixes: cf28264196e5 "virtio-serial: Rework shutdown sequence" Signed-off-by: Greg Kurz <groug@kaod.org> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'board-qemu/slof/virtio-serial.fs')
-rw-r--r--board-qemu/slof/virtio-serial.fs14
1 files changed, 11 insertions, 3 deletions
diff --git a/board-qemu/slof/virtio-serial.fs b/board-qemu/slof/virtio-serial.fs
index ac55ffc..06bfe76 100644
--- a/board-qemu/slof/virtio-serial.fs
+++ b/board-qemu/slof/virtio-serial.fs
@@ -19,9 +19,11 @@ virtio-setup-vd VALUE virtiodev
\ Quiescence the virtqueue of this device so that no more background
\ transactions can be pending.
: shutdown ( -- )
- virtiodev virtio-serial-shutdown
- FALSE to initialized?
- 0 to virtiodev
+ initialized? IF
+ virtiodev virtio-serial-shutdown
+ FALSE to initialized?
+ 0 to virtiodev
+ THEN
;
: virtio-serial-term-emit
@@ -31,10 +33,16 @@ virtio-setup-vd VALUE virtiodev
: virtio-serial-term-key? virtiodev virtio-serial-haschar ;
: virtio-serial-term-key BEGIN virtio-serial-term-key? UNTIL virtiodev virtio-serial-getchar ;
+: virtio-serial-close-stdout s" stdout" get-chosen IF decode-int nip nip close-dev THEN ;
+
\ Basic device initialization - which has only to be done once
: init ( -- )
virtiodev virtio-serial-init drop
TRUE to initialized?
+ \ Linux closes stdin at some point in prom_init(). This internally triggers a
+ \ quiesce in SLOF. We must ensure stdout gets closed as well otherwise the
+ \ device cannot be reset properly and the boot will hang.
+ ['] virtio-serial-close-stdout add-quiesce-xt
;
0 VALUE open-count