From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Gordan Bobic <gordan@bobich.net>
Cc: xen-devel@lists.xen.org
Subject: Re: USB passthrough burning 5% of CPU?
Date: Mon, 5 Aug 2013 11:44:35 -0400 [thread overview]
Message-ID: <20130805154435.GK3321@phenom.dumpdata.com> (raw)
In-Reply-To: <446278be57f7b83e771e9306f7172d96@mail.shatteredsilicon.net>
On Mon, Aug 05, 2013 at 01:28:39PM +0100, Gordan Bobic wrote:
> Ever since I switched from passing a PCI USB controller
> through to a domU in favour of passing USB devices using
> the "usbdevice" config parameter, the domU affected
> seems to have qemu-dm "idling" at about 5% CPU usage in
> dom0. With the PCI USB controller passed through, this
> does not happen.
>
> Is this normal/expected? Does a similar continuous CPU
> overhead invisibly apply to PCI passthrough devices as
> well? Or is this CPU tax only applicable to USB
> passthrough?
I think that is about right. USB1 sucks at virtualization so
QEMU has to scan a list of memory regions to figure out if
the guest has decided that "hey, I've a got a packet of
data'. The CPU overhead for PCI passthrough does not happen
as the PCI device can detect where the request went and
do it stuff.
USB2.0 is not any better either. The XHCI on the other hand
is - but I am not sure if that is implemented in QEMU yet.
Ah, Gerd here has a nice update:
http://www.linux-kvm.org/wiki/images/b/be/2012-forum-qemu-usb-status-update.pdf
>
> Gordan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-08-05 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:28 USB passthrough burning 5% of CPU? Gordan Bobic
2013-08-05 13:57 ` George Dunlap
2013-08-05 14:01 ` Gordan Bobic
2013-08-05 14:16 ` George Dunlap
2013-08-05 13:59 ` Ian Campbell
2013-08-05 15:44 ` Konrad Rzeszutek Wilk [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=20130805154435.GK3321@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gordan@bobich.net \
--cc=xen-devel@lists.xen.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).