diff options
Diffstat (limited to 'results/classifier/108/other/1213196')
| -rw-r--r-- | results/classifier/108/other/1213196 | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/108/other/1213196 b/results/classifier/108/other/1213196 new file mode 100644 index 000000000..624298f8e --- /dev/null +++ b/results/classifier/108/other/1213196 @@ -0,0 +1,39 @@ +socket: 0.799 +semantic: 0.557 +device: 0.523 +network: 0.502 +graphic: 0.422 +other: 0.410 +performance: 0.408 +PID: 0.337 +files: 0.328 +vnc: 0.323 +boot: 0.251 +permissions: 0.218 +KVM: 0.146 +debug: 0.145 + +-serial tcp should hang up when DTR goes low + +In keeping with the spirit of serial modem control signals, de-asserting DTR should cause the TCP connection to break; asserting DTR should cause QEMU to initiate a new connection or for it to accept another (in server mode; this may involve waiting for one to arrive, too). + +In addition to allowing low DTR to drop the socket connection, and allowing low DTR to reject a socket connection, the DCD modem bit also be implemented - DCD should follow the state of the TCP socket: a connected socket should pull DCD high, and a disconnected socket should pull DCD low. From what Ive seen in the source, it looks like a serial IOCTL functioned needs to be added to chardev/char-socket.c to allow the MSR bits to be tracked against the state of the socket. DCD should be very easy to implement this way, but I hadn't thought about DTR. + +Sent in a patch for this. + +https://lists.gnu.org/archive/html/qemu-devel/2020-12/msg04658.html + +DTR controls the socket. + +DCD reflects the state of the socket. + + + + +This is an automated cleanup. This bug report has been moved to QEMU's +new bug tracker on gitlab.com and thus gets marked as 'expired' now. +Please continue with the discussion here: + + https://gitlab.com/qemu-project/qemu/-/issues/97 + + |