From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] qemu-options.hx: Improve documentation of chardev multiplexing mode
Date: Tue, 16 Feb 2016 09:27:50 -0700 [thread overview]
Message-ID: <56C34E06.6050904@redhat.com> (raw)
In-Reply-To: <1455638581-5912-1-git-send-email-peter.maydell@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On 02/16/2016 09:03 AM, Peter Maydell wrote:
> The current documentation of chardev mux=on is rather brief and opaque;
> expand it to hopefully be a bit more helpful.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> There was some discussion on #qemu yesterday evening about multiplexing,
> and "make the docs a bit less confusing" was one suggestion...
> ---
> qemu-options.hx | 20 +++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
Looks like a strict improvement, so:
Reviewed-by: Eric Blake <eblake@redhat.com>
That said, how does one enter a literal <ctrl-a> to the front end,
instead of getting it interpreted by the mux backend as a signal of
whether to rotate to the next front end? Is <ctrl-a> an escaping
character, such that sending it twice results in a single instance being
sent to the current guest front end hooked up to the mux?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-02-16 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 16:03 [Qemu-devel] [PATCH] qemu-options.hx: Improve documentation of chardev multiplexing mode Peter Maydell
2016-02-16 16:20 ` Paolo Bonzini
2016-02-16 16:27 ` Eric Blake [this message]
2016-02-16 16:32 ` Laszlo Ersek
2016-02-16 17:02 ` Paolo Bonzini
2016-02-16 17:57 ` Laszlo Ersek
2016-02-16 18:07 ` Peter Maydell
2016-02-16 16:36 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C34E06.6050904@redhat.com \
--to=eblake@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).