diff options
| author | Adam Litke <agl@us.ibm.com> | 2010-01-15 08:34:02 -0600 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2010-01-19 16:31:04 -0600 |
| commit | f039a563f200beee80cc10fd70b21ea396979dab (patch) | |
| tree | d80ee92a06d613f01a26766f5859173a69ad202f /hw/ide | |
| parent | beb6f0de7aa19ce62fdd21a876b8c171ac7fde2e (diff) | |
| download | qemu-f039a563f200beee80cc10fd70b21ea396979dab.zip qemu-f039a563f200beee80cc10fd70b21ea396979dab.tar.gz qemu-f039a563f200beee80cc10fd70b21ea396979dab.tar.bz2 | |
QMP: Emit asynchronous events on all QMP monitors
When using a control/QMP monitor in tandem with a regular monitor, asynchronous
messages can get lost depending on the order of the QEMU program arguments.
QEMU events issued by monitor_protocol_event() always go to cur_mon. If the
user monitor was specified on the command line first (or it has ,default), the
message will be directed to the user monitor (not the QMP monitor).
Additionally, only one QMP session is currently able to receive async messages.
To avoid this confusion, scan through the list of monitors and emit the message
on each QMP monitor.
Signed-off-by: Adam Litke <agl@us.ibm.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/ide')
0 files changed, 0 insertions, 0 deletions