Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 94
hw/virtio-serial.h
Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 91
hw/virtio-serial.c
Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 91
hw/virtio-serial.c
Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 73
hw/virtio-serial.c
On (Wed) Dec 23 2009 [17:14:28], Anthony Liguori wrote:
>
>> +/*
>> + * Items in struct VirtIOSerialPort.
>> + */
>> +QTAILQ_FOREACH(port,&s->ports, next) {
>> +/*
>> + * We put the port number because we may not have an active
>> + * port at id 0 that's rese
On 12/23/2009 01:52 PM, Amit Shah wrote:
Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 73
Via control channel messages, the guest can tell us whether a port got
opened or closed. Similarly, we can also indicate to the guest of host
port open/close events.
Signed-off-by: Amit Shah
---
hw/virtio-serial-bus.c | 73
hw/virtio-serial.c
