On 05/28/2013 12:34 AM, Gerd Hoffmann wrote:
Fill unset CharDriverState-filename with the backend name, so
'info chardev' will return at least the chardev type. Don't
touch it in case the chardev init function filled it already,
like the socket+pty chardevs do for example.
Signed-off-by:
On 05/31/13 14:36, Eric Blake wrote:
On 05/28/2013 12:34 AM, Gerd Hoffmann wrote:
Fill unset CharDriverState-filename with the backend name, so
'info chardev' will return at least the chardev type. Don't
touch it in case the chardev init function filled it already,
like the socket+pty
Hi,
Without this patch the returned message for query-chardev is:
{
return: [
{
filename: pty:/dev/pts/8,
label: charserial0
},
{
filename: unix:/var/lib/libvirt/qemu/qemu-git.monitor,server,
label:
On 05/31/13 15:21, Gerd Hoffmann wrote:
Hi,
Hi,
Please double-check. Current master
(87d23f78aa79b72da022afda358bbc8a8509ca70 to be exact) works just fine
for me. libvirt works, including a serial line redirected to pty, and
'info chardev' looks sane too.
sorry for the fuzz. :/
Fill unset CharDriverState-filename with the backend name, so
'info chardev' will return at least the chardev type. Don't
touch it in case the chardev init function filled it already,
like the socket+pty chardevs do for example.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
qemu-char.c |
On 05/28/13 08:34, Gerd Hoffmann wrote:
Fill unset CharDriverState-filename with the backend name, so
'info chardev' will return at least the chardev type. Don't
touch it in case the chardev init function filled it already,
like the socket+pty chardevs do for example.
Signed-off-by: Gerd
Fill unset CharDriverState-filename with the backend name, so
'info chardev' will return at least the chardev type. Don't
touch it in case the chardev init function filled it already,
like the socket+pty chardevs do for example.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
qemu-char.c |
