Date: Mon, 11 Jul 2016 20:36:37 +0200 From: Jakub Klama <jakub.klama@uj.edu.pl> To: Paul Vixie <paul@redbarn.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: [Differential] D7185: Add virtio-console support to bhyve Message-ID: <6B5AEBF8-98B0-4031-A3E3-A1EBC8B4B763@uj.edu.pl> In-Reply-To: <5783E64B.9010608@redbarn.org> References: <differential-rev-PHID-DREV-h346qsj6dfo524z3qnfy-req@FreeBSD.org> <5783D6FF.7010107@redbarn.org> <FCF5C7E6-2BCF-4729-BC2B-788E1FE74BCE@uj.edu.pl> <5783E2FE.1040309@redbarn.org> <EDFB1E4C-755F-4D2F-808C-E45A31C3EE2C@uj.edu.pl> <5783E64B.9010608@redbarn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Wiadomo=C5=9B=C4=87 napisana przez Paul Vixie <paul@redbarn.org> w = dniu 11.07.2016, o godz. 20:32: >>> nmdm could theoretically (as pty and pts both do) support >>> TIOCGWINSZ and SIGWINCH, though? or perhaps bhyve's virtio_console >>> device could offer pts(4) support? >>=20 >> Yeah, virtio_console totally deserves support for binding virtual >> console to a pty/pts. >=20 > layering wise, adding TIOCGWINSZ and SIGWINCH support to nmdm makes = more sense than inventing another host-side protocol. as does adding = pts(4) support to the virtio_console driver. are those things hard? nmdm(4) emulates a serial port. how could one pass ioctls and signals = via serial port? >>> is the protocol spoken over the virtio_console socket documented >>> online? i'd like to add support to rtty. currently i've been >>> running the "resize" command at the guest shell, which feels very >>> primitive. >>=20 >> Right now the socket just speaks raw data. It would need some >> multiplexing or ideally an IPC mechanism to send the resize events. >=20 > yikes. so you've got to reinvent what TIOCPKT does, but differently? how could one pass ioctls via unix domain socket? Jakub=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B5AEBF8-98B0-4031-A3E3-A1EBC8B4B763>