qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] questions about host side of virtio-serial
Date: Wed, 30 Jul 2014 12:52:41 -0600	[thread overview]
Message-ID: <53D93EF9.3020505@windriver.com> (raw)

Hi,

I'm working on a native user of virtio-serial (ie, not going via the 
qemu guest agent).

The information at "http://www.linux-kvm.org/page/Virtio-serial_API" 
does a good job of describing the guest side of things, but has very 
little information about the host side of things.

In particular, assuming that the host side is using a chardev mapped to 
a unix socket:

1) Is there any way for the host app to get information about whether or 
not the guest is reading the messages?  (i.e. logically equivalent to 
getting POLLHUP in the guest when the host app disconnects.)

2) Suppose the host sends a large message.  The guest app reads a 
portion of the message, then crashes.  We respawn the guest app and 
start reading again, but now we're in the middle of a message of 
arbitrary size.  Is there a recommended technique to re-sync the host 
and guest?

3) Same as 2, but the guest sending to the host and the host app 
crashing partway through.

4) If nothing in the guest is reading the data, how much data can the 
host send before it will get an error?  Is there a way to adjust this?

Thanks,
Chris

             reply	other threads:[~2014-07-30 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 18:52 Chris Friesen [this message]
2014-07-31  9:32 ` [Qemu-devel] questions about host side of virtio-serial Richard W.M. Jones
2014-07-31 14:45   ` Chris Friesen
2014-07-31 15:07     ` Paolo Bonzini

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=53D93EF9.3020505@windriver.com \
    --to=chris.friesen@windriver.com \
    --cc=amit.shah@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).