From: Max Krasnyansky <maxk@kernel.org>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] EHCI (usb 2.0) support
Date: Fri, 05 Sep 2008 22:54:00 -0700 [thread overview]
Message-ID: <48C21AF8.3040803@kernel.org> (raw)
With my latest USB patches, that I just sent out, UHCI support is probably as
good as it gets. I tested all kinds of devices with Linux and XP guests and
things are solid.
Host USB is now fully async and I do not see any delays/jerkiness anymore.
However, overall performance can certainly be improved by supporting EHCI (ie
usb-2.0 stuff). For example native performance of an external USB hard drive
is ~28MB/sec (measured with hdparm). The same drive attached to the Linux
guest gives me about 500KB/sec. Huge difference.
So I'm going to start working on EHCI (starting tomorrow). If somebody has any
EHCI code I can use let me know.
Max
next reply other threads:[~2008-09-06 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 5:54 Max Krasnyansky [this message]
2008-09-07 6:31 ` [Qemu-devel] EHCI (usb 2.0) support Arnon Gilboa
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=48C21AF8.3040803@kernel.org \
--to=maxk@kernel.org \
--cc=kvm@vger.kernel.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).