From: Gordan Bobic <gordan@bobich.net>
To: xen-devel@lists.xen.org
Subject: USB passthrough burning 5% of CPU?
Date: Mon, 05 Aug 2013 13:28:39 +0100 [thread overview]
Message-ID: <446278be57f7b83e771e9306f7172d96@mail.shatteredsilicon.net> (raw)
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?
Gordan
next reply other threads:[~2013-08-05 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:28 Gordan Bobic [this message]
2013-08-05 13:57 ` USB passthrough burning 5% of CPU? 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
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=446278be57f7b83e771e9306f7172d96@mail.shatteredsilicon.net \
--to=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).