From: Amit Shah <amit.shah@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Amos Kong <akong@redhat.com>, qemu list <qemu-devel@nongnu.org>,
marcandre.lureau@redhat.com,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/1] virtio: serial: expose a 'guest_writable' callback for users
Date: Fri, 14 Nov 2014 07:18:08 +0530 [thread overview]
Message-ID: <20141114014808.GF14495@grmbl.mre> (raw)
In-Reply-To: <1415890032.25539.19.camel@nilsson.home.kraxel.org>
On (Thu) 13 Nov 2014 [15:47:12], Gerd Hoffmann wrote:
> On Di, 2014-10-28 at 20:21 +0530, Amit Shah wrote:
> > Users of virtio-serial may want to know when a port becomes writable. A
> > port can stop accepting writes if the guest port is open but not being
> > read from. In this case, data gets queued up in the virtqueue, and
> > after the vq is full, writes to the port do not succeed.
> >
> > When the guest reads off a vq element, and adds a new one for the host
> > to put data in, we can tell users the port is available for more writes,
> > via the new ->guest_writable() callback.
> >
> > Signed-off-by: Amit Shah <amit.shah@redhat.com>
>
> What is the plan with that one? I have some spice patches sitting in a
> branch depending on this one. Should it go through virtio queue? With
> some ack from virtio I can also take it through the spice queue,
> together with the other patches depending on this one.
I will push it through my tree when 2.3 opens.
> It fails checkpatch btw:
Yes, v4 (in the pull req) corrected this.
Thanks,
Amit
prev parent reply other threads:[~2014-11-14 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 14:51 [Qemu-devel] [PATCH v3 1/1] virtio: serial: expose a 'guest_writable' callback for users Amit Shah
2014-10-28 15:18 ` Marc-André Lureau
2014-11-13 14:47 ` Gerd Hoffmann
2014-11-13 14:52 ` Peter Maydell
2014-11-13 14:56 ` Gerd Hoffmann
2014-11-14 1:48 ` Amit Shah [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=20141114014808.GF14495@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--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).