qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make -qmp stdio usable
Date: Mon, 23 Aug 2010 08:22:47 +0200	[thread overview]
Message-ID: <4C7213B7.20007@redhat.com> (raw)
In-Reply-To: <4C719B8D.1010208@codemonkey.ws>

On 08/22/2010 11:50 PM, Anthony Liguori wrote:
> On 08/11/2010 04:56 PM, Paolo Bonzini wrote:
>> Currently -qmp stdio (or the equivalent -mon/-chardev combination) sets
>> up the terminal attributes even though it does not go through readline
>> to actually do I/O. As a result, echo is disabled and you cannot see
>> anything you type. This patch fixes it by adding a "cooked" option to
>> the stdio chardev backend, that when set will disable switching the tty
>> to raw mode.
>
> cooked doesn't make a whole lot of sense to me (and it's not documented
> anywhere).

"Cooked mode" is actually pretty common when talking about the Unix 
TTYs, I can find it for example in curses documentation:

     Normally,  the  tty  driver buffers typed characters until a
     newline or carriage return is typed.  The cbreak routine disables
     line  buffering and erase/kill character-processing (interrupt and
     flow control characters are unaffected), making characters typed by
     the  user  immediately available to the program.  The nocbreak
     routine returns the terminal to normal (cooked) mode.

> Maybe raw=on|off or even echo=on|off would make more sense?

raw would make sense, echo was my first choice but it has the problem 
that echo is done anyway when Qemu's readline is involved.

I'll redo the patch with raw.

Paolo

      reply	other threads:[~2010-08-23  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 21:56 [Qemu-devel] [PATCH] make -qmp stdio usable Paolo Bonzini
2010-08-22 21:50 ` Anthony Liguori
2010-08-23  6:22   ` Paolo Bonzini [this message]

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=4C7213B7.20007@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).