From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 03/13] usb-host-libusb: Detach kernel drivers earlier
Date: Wed, 09 Oct 2013 10:55:39 +0200 [thread overview]
Message-ID: <1381308939.12583.27.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1381262298-3241-4-git-send-email-hdegoede@redhat.com>
On Di, 2013-10-08 at 21:58 +0200, Hans de Goede wrote:
> If we detach the kernel drivers on the first set_config, then they will
> be still attached when the device gets its initial reset. Causing the drivers
> to re-initialize the device after the reset, dirtying the device state.
> @@ -1051,7 +1055,6 @@ static void usb_host_set_config(USBHostDevice *s, int config, USBPacket *p)
> trace_usb_host_set_config(s->bus_num, s->addr, config);
>
> usb_host_release_interfaces(s);
> - usb_host_detach_kernel(s);
> rc = libusb_set_configuration(s->dh, config);
> if (rc != 0) {
> usb_host_libusb_error("libusb_set_configuration", rc);
Sure we can safely remove the detach_kernel here?
Assuming we have a device with multiple configurations, each
configuration has a different set of interfaces, guest switches from one
config to another. Do we correctly unbind kernel / claim interfaces
then?
Handling this correctly was the reason to do the kernel unbind in
response to the guests set_config instead of host_open btw, although I
can see the issues the late unbind introduces.
cheers,
Gerd
next prev parent reply other threads:[~2013-10-09 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 19:58 [Qemu-devel] [PATCH 00/13] usb: Add support for bulk streams to usb-host-libusb Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 01/13] usb-host-libusb: Fix reset handling Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 02/13] usb-host-libusb: Configuration 0 may be a valid configuration Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 03/13] usb-host-libusb: Detach kernel drivers earlier Hans de Goede
2013-10-09 8:55 ` Gerd Hoffmann [this message]
2013-10-09 13:08 ` Hans de Goede
2013-10-09 13:35 ` Gerd Hoffmann
2013-10-09 15:34 ` Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 04/13] usb-hcd-xhci: Remove unused sstreamsm member from XHCIStreamContext Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 05/13] usb-hcd-xhci: Remove unused cancelled member from XHCITransfer Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 06/13] usb-hcd-xhci: Report completion of active transfer with CC_STOPPED on ep stop Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 07/13] usb-hcd-xhci: Update endpoint context dequeue pointer for streams too Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 08/13] usb: Add max_streams attribute to endpoint info Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 09/13] usb: Add usb_device_alloc/free_streams Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 10/13] xhci: Call usb_device_alloc/free_streams Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 11/13] usb-host-libusb: Fill in endpoint max_streams when available Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 12/13] usb-host-libusb: Add alloc / free streams ops Hans de Goede
2013-10-08 19:58 ` [Qemu-devel] [PATCH 13/13] usb-host-libusb: Set stream id when submitting bulk-stream transfers 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=1381308939.12583.27.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=hdegoede@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).