Marc-André Lureau f7ea2038be char-pty: remove write_lock usage ... The lock usage was described with its introduction in commit 9005b2a758. It was necessary because PTY write() shares more state than GIOChannel with other operations. This made char-pty a bit different from other chardev, that only lock around the write operation. This was apparent in commit 7b3621f47a, which introduced an idle source to avoid the lock. By removing the PTY chardev state sharing on write() with previous patch, we can remove the lock and the idle source. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <20190206174328.9736-7-marcandre.lureau@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>		2019-02-13 16:46:39 +01:00
..
baum.c
char-console.c
char-fd.c
char-fe.c	char: update the mux handlers in class callback	2019-02-13 15:36:14 +01:00
char-file.c
char-io.c
char-mux.c	char: update the mux handlers in class callback	2019-02-13 15:36:14 +01:00
char-null.c
char-parallel.c
char-pipe.c
char-pty.c	char-pty: remove write_lock usage	2019-02-13 16:46:39 +01:00
char-ringbuf.c
char-serial.c	chardev: ensure termios is fully initialized	2019-02-12 17:35:56 +01:00
char-socket.c
char-stdio.c
char-udp.c
char-win-stdio.c
char-win.c
char.c	char: allow specifying a GMainContext at opening time	2019-02-13 14:23:39 +01:00
Makefile.objs
msmouse.c
spice.c
testdev.c
trace-events
wctablet.c	chardev/wctablet: Fix a typo	2019-02-13 14:31:31 +01:00