All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/7] usb: remove old usb-host code
Date: Fri, 08 Nov 2013 15:00:00 +0100	[thread overview]
Message-ID: <527CEE60.5020109@siemens.com> (raw)
In-Reply-To: <1381318925.12583.82.camel@nilsson.home.kraxel.org>

On 2013-10-09 13:42, Gerd Hoffmann wrote:
>   Hi,
> 
>>>> Only very recent distros fulfill the need of >= 1.0.13, so you naturally
>>>> fall back to this code. I just realized that even the factory build of
>>>> OpenSUSE is still on libusb-1.0.9. Current Ubuntu versions are on 1.0.12
>>>> at best. Didn't check others so far.
>>>
>>> Ouch.  The 1.0.13 release is one year old by now.
>>>
>>> Fedora 19 is at 1.0.16 btw.
>>>
>>>> So isn't this step a bit too early?
>>>
>>> There is always the 'git revert' option in case it turns out there are
>>> too many issues ...
>>
>> So what to do? Do you expect all the other distros to catch up regarding
>> libusb until QEMU 1.7 is released?
> 
> They will update once they figure this is needed for qemu 1.7 :)
> Updates will probably not yet be available at release time though.
> 
> If we revert, thereby continue fallback to the old code, chances are
> high that nothing happens and we'll face the same issue for qemu 1.8.
> 
> Given that there are some known issues in the host-linux code which are
> fixed in host-libusb I really want get rid of it.

OK, then here is the first issue I ran into while trying libusbx (git
head, i.e. 1.0.17+: The new stack causes significant latency issues that
makes it almost unusable for pass-through of USB audio devices (some
headset in my case). Reverting usb-linux and disabling libusb over QEMU
git head makes things work again. I'll have to stick with this for now
as it is affecting my work environment.

Any spontaneous ideas how to analyse or even resolve this?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-11-08 14:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19  9:34 [Qemu-devel] [PULL 0/7] usb patch queue Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 1/7] usb: remove old usb-host code Gerd Hoffmann
2013-10-02 13:14   ` Jan Kiszka
2013-10-07  7:16     ` Gerd Hoffmann
2013-10-09 10:55       ` Jan Kiszka
2013-10-09 11:42         ` Gerd Hoffmann
2013-11-08 14:00           ` Jan Kiszka [this message]
2013-11-08 15:39             ` Gerd Hoffmann
2013-11-08 16:51               ` Jan Kiszka
2013-11-11  8:47                 ` Gerd Hoffmann
2013-11-11 19:28                   ` Hans de Goede
2013-09-19  9:34 ` [Qemu-devel] [PATCH 2/7] xhci: Fix number of streams allocated when using streams Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 3/7] xhci: Init a transfers xhci, slotid and epid member on epctx alloc Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 4/7] xhci: Add xhci_epid_to_usbep helper function Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 5/7] xhci: Fix memory leak on xhci_disable_ep Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 6/7] usb: Also reset max_packet_size on ep_reset Gerd Hoffmann
2013-09-19  9:34 ` [Qemu-devel] [PATCH 7/7] usb: Fix iovec memleak on combined-packet free Gerd Hoffmann

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=527CEE60.5020109@siemens.com \
    --to=jan.kiszka@siemens.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.