From: Paolo Bonzini <pbonzini@redhat.com>
To: "Eric S. Johansson" <esj@eggo.org>, kvm@vger.kernel.org
Subject: Re: just an observation about USB
Date: Wed, 14 Oct 2015 22:04:00 +0200 [thread overview]
Message-ID: <561EB530.6010605@redhat.com> (raw)
In-Reply-To: <561EAF76.1010105@eggo.org>
On 14/10/2015 21:39, Eric S. Johansson wrote:
> update from the NaturallySpeaking in a VM project.
>
> don't remember what I told you before but, yes I can now send keystroke
> events generated by speech recognition in the Windows guest into the
> Linux input queue. I can also extract information from the Linux side,
> and have it modify the grammar on the Windows side. The result of
> activating that grammar is that I can execute code on either side in
> response to speech recognition commands. it's fragile as all hell but
> I'm the only one using it so far. :-)
That's awesome! What was the problem?
> Latency is a bit longer than I like. USB and network connections break
> every time I come out of suspend part at least I don't have to use
> Windows all the time.
>
> One thing is puzzling though. Windows, in idle, consume something like
> 15 to 20% CPU according to top. I turn on NaturallySpeaking, the
> utilization climbs to him roughly 30 to 40%. I turn on the microphone
> and utilization jumps up to 80-110%. In other words, it takes up a
> whole core.
USB is really expensive because it's all done through polling. Do that
in hardware, and your computer is a bit hotter; do that in software
(that's what VMs do) and your computer doubles as a frying pan.
If you have USB3 drivers in Windows, you can try using a USB3
controller. But it's probably going to waste a lot of processing power
too, because USB audio uses a lot of small packets, making it basically
the worst case.
Paolo
next prev parent reply other threads:[~2015-10-14 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 19:39 just an observation about USB Eric S. Johansson
2015-10-14 20:04 ` Paolo Bonzini [this message]
2015-10-14 20:30 ` Eric S. Johansson
2015-10-16 11:55 ` Stefan Hajnoczi
2015-10-16 15:48 ` Eric S. Johansson
2015-10-19 8:02 ` 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=561EB530.6010605@redhat.com \
--to=pbonzini@redhat.com \
--cc=esj@eggo.org \
--cc=kvm@vger.kernel.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).