aboutsummaryrefslogtreecommitdiff
path: root/qemu-char.c
diff options
context:
space:
mode:
authorAmit Shah <amit.shah@redhat.com>2009-11-03 19:59:55 +0530
committerAnthony Liguori <aliguori@us.ibm.com>2009-11-17 08:03:30 -0600
commit57e073a3a152d0e63c3df257c60ababb19f2c13d (patch)
tree0cc9772c7c7904ccb5ff71b4d8982c59d554bcef /qemu-char.c
parent9bd7854e1e5d6f4cfe4558090bbd9493c12bf846 (diff)
downloadqemu-57e073a3a152d0e63c3df257c60ababb19f2c13d.zip
qemu-57e073a3a152d0e63c3df257c60ababb19f2c13d.tar.gz
qemu-57e073a3a152d0e63c3df257c60ababb19f2c13d.tar.bz2
char: Remove special init_reset handling
The initial_reset sent to chardevs doesn't do much other than setting a bool to true. Char devices are interested in the open event and that gets sent whenever the device is opened. Moreover, the reset logic breaks as and when qemu's bh scheduling changes. Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'qemu-char.c')
-rw-r--r--qemu-char.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/qemu-char.c b/qemu-char.c
index 1f630195..d78bae3 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -128,15 +128,6 @@ void qemu_chr_reset(CharDriverState *s)
}
}
-void qemu_chr_initial_reset(void)
-{
- CharDriverState *chr;
-
- QTAILQ_FOREACH(chr, &chardevs, next) {
- qemu_chr_reset(chr);
- }
-}
-
int qemu_chr_write(CharDriverState *s, const uint8_t *buf, int len)
{
return s->chr_write(s, buf, len);