From: Hans de Goede <hdegoede@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] usb-redir: Call qemu_chr_guest_open/close
Date: Sun, 07 Aug 2011 19:41:32 +0200 [thread overview]
Message-ID: <4E3ECE4C.10805@redhat.com> (raw)
In-Reply-To: <4E3EB4CE.8030201@codemonkey.ws>
Hi,
On 08/07/2011 05:52 PM, Anthony Liguori wrote:
> On 08/07/2011 08:21 AM, Hans de Goede wrote:
>> To let the chardev now we're ready start receiving data. This is necessary
>> with the spicevmc chardev to get it registered with the spice-server.
>>
>> Signed-off-by: Hans de Goede<hdegoede@redhat.com>
>> ---
>> usb-redir.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/usb-redir.c b/usb-redir.c
>> index e212993..ec88c0b 100644
>> --- a/usb-redir.c
>> +++ b/usb-redir.c
>> @@ -809,6 +809,8 @@ static int usbredir_initfn(USBDevice *udev)
>>
>> qemu_chr_add_handlers(dev->cs, usbredir_chardev_can_read,
>> usbredir_chardev_read, usbredir_chardev_event, dev);
>> + /* Let the other side know we are ready */
>> + qemu_chr_guest_open(dev->cs);
>
>
> You should do guest_open before adding handlers.
Erm, no, guest_open may lead to a callback in the
chardev, to which it may respond by immediately queuing a few writes /
doing a read. To me it makes much more sense to actually call guest_open
when we are ready to receive data / to be read from, rather then to do
it before our handlers are hooked up and thus before we are ready.
Regards,
Hans
next prev parent reply other threads:[~2011-08-07 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 13:21 [Qemu-devel] [PATCH 1/3] spice-qemu-char: Generate chardev open/close events Hans de Goede
2011-08-07 13:21 ` [Qemu-devel] [PATCH 2/3] usb-redir: Call qemu_chr_guest_open/close Hans de Goede
2011-08-07 15:52 ` Anthony Liguori
2011-08-07 17:41 ` Hans de Goede [this message]
2011-08-07 21:30 ` Anthony Liguori
2011-08-08 8:01 ` Hans de Goede
2011-08-08 12:52 ` Anthony Liguori
2011-08-08 13:03 ` Hans de Goede
2011-08-08 13:08 ` Anthony Liguori
2011-08-07 13:21 ` [Qemu-devel] [PATCH 3/3] usb-redir: Device disconnect + re-connect robustness fixes Hans de Goede
2011-08-07 15:52 ` [Qemu-devel] [PATCH 1/3] spice-qemu-char: Generate chardev open/close events Anthony Liguori
2011-08-07 17:39 ` Hans de Goede
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=4E3ECE4C.10805@redhat.com \
--to=hdegoede@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@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).