Re: [Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon

2013-07-29 Thread Michael Roth
Quoting Michael Tokarev (2013-07-29 06:26:20) > Can we try to fix this for 1.6 please? :) > Or should I try to cook up a patch? Hmm, this seems to be a little less straight-forward than I thought. We can't defer OPENED till after MUX_OUT ad infinitum since this will cause the latest FE to be added

Re: [Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon

2013-07-29 Thread Michael Tokarev
Can we try to fix this for 1.6 please? :) Or should I try to cook up a patch? Thanks, /mjt 04.07.2013 01:06, Michael Roth wrote: On Wed, Jul 3, 2013 at 1:03 AM, Michael Tokarev wrote: Before commit bd5c51ee6c4f1c79cae5ad2516d711a27b4ea8ec Author: Michael Roth Date: Fri Jun 7 15:19:53 201

Re: [Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon

2013-07-03 Thread Michael Roth
On Wed, Jul 3, 2013 at 1:03 AM, Michael Tokarev wrote: > Before > > commit bd5c51ee6c4f1c79cae5ad2516d711a27b4ea8ec > Author: Michael Roth > Date: Fri Jun 7 15:19:53 2013 -0500 > > qemu-char: don't issue CHR_EVENT_OPEN in a BH > > we had no echo by default with -nographic, and it gave > the

[Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon

2013-07-02 Thread Michael Tokarev
Before commit bd5c51ee6c4f1c79cae5ad2516d711a27b4ea8ec Author: Michael Roth Date: Fri Jun 7 15:19:53 2013 -0500 qemu-char: don't issue CHR_EVENT_OPEN in a BH we had no echo by default with -nographic, and it gave the prompt when switching to monitor: $ qemu-system-x86_64 -nographic _