From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] questions about host side of virtio-serial
Date: Thu, 31 Jul 2014 17:07:50 +0200 [thread overview]
Message-ID: <53DA5BC6.7040404@redhat.com> (raw)
In-Reply-To: <53DA5675.6010607@windriver.com>
Il 31/07/2014 16:45, Chris Friesen ha scritto:
> With qemu 1.4.2 it blocks or returns EAGAIN if the guest tries to write
> to the char device, but the behaviour is different if the host tries to
> write to the unix socket. See 4 below.
1.4.2 is too old. Even CentOS 6's franken-0.12 would be preferrable to
such an old release, in particular it had the flow control patches from
1.5.0 backported.
Paolo
prev parent reply other threads:[~2014-07-31 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 18:52 [Qemu-devel] questions about host side of virtio-serial Chris Friesen
2014-07-31 9:32 ` Richard W.M. Jones
2014-07-31 14:45 ` Chris Friesen
2014-07-31 15:07 ` 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=53DA5BC6.7040404@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=chris.friesen@windriver.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).