Searched hist:"20 f4aa265ec8442be66f00ee3986a92018b44b7b" (Results 1 – 3 of 3) sorted by relevance
| /qemu/io/ |
| H A D | channel.c | 20f4aa265ec8442be66f00ee3986a92018b44b7b Fri Sep 30 10:50:18 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: add ability to set a name for IO channels
The GSource object has ability to have a name, which is useful
when debugging performance problems with the mainloop event
callbacks that take too long. By associating a name with a
QIOChannel object, we can then set the name on any GSource
associated with the channel.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|
| /qemu/include/io/ |
| H A D | channel.h | 20f4aa265ec8442be66f00ee3986a92018b44b7b Fri Sep 30 10:50:18 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: add ability to set a name for IO channels
The GSource object has ability to have a name, which is useful
when debugging performance problems with the mainloop event
callbacks that take too long. By associating a name with a
QIOChannel object, we can then set the name on any GSource
associated with the channel.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|
| /qemu/include/ |
| H A D | glib-compat.h | 20f4aa265ec8442be66f00ee3986a92018b44b7b Fri Sep 30 10:50:18 UTC 2016 Daniel P. Berrange <berrange@redhat.com> io: add ability to set a name for IO channels
The GSource object has ability to have a name, which is useful
when debugging performance problems with the mainloop event
callbacks that take too long. By associating a name with a
QIOChannel object, we can then set the name on any GSource
associated with the channel.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
|