From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: high load with win7 & usb tablet
Date: Fri, 10 Sep 2010 15:50:46 +0300 [thread overview]
Message-ID: <4C8A29A6.60108@redhat.com> (raw)
In-Reply-To: <4C8A282A.5010506@msgid.tls.msk.ru>
On 09/10/2010 03:44 PM, Michael Tokarev wrote:
> 10.09.2010 16:19, Avi Kivity wrote:
>> On 09/03/2010 03:21 PM, Michael Tokarev wrote:
>>> Hello.
>>>
>>> I noticed that window7, unlike windowsXP as I played with
>>> previously, poses quite high load on host when idle. On
>>> my machine, host cpu usage is about 25% when one single-cpu
>>> win7 guest is running with "-usbdevice tablet" option.
>>> Here's a typical kvm_stats when such a guest is idling:
> []
>> That's pretty good for an idle guest.
> Hm. Well. Sometimes it goes "a bit" further than that:
>
> efer_reload 0 0
> exits 6307547 12445
This still isn't worth 25% cpu.
>> What does the guest think it is doing? The Windows performance monitor?
> Nothing. It shows perfmon.exe using 3% CPU, and that's about
> it. I'm attaching a .png screenshot of the KVM window with
> w7 perfmon running. Unfortunately I don't have English
> version handy, it's all in Russian, and I weren't able to
> change system language to English. But it is still readable.
>
> During this shot, host CPU was about 30..35% in use - higher
> than usual 25%, but I guess it's due to perfmon.
Please build qemu with --disable-strip and use 'perf' to profile it.
> Also, I haven't found a way to see, for example, individual
> interrupt activity in windows (like /proc/interrupts in
> linux).
irq_injections is very low anyway.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-09-10 12:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 12:21 high load with win7 & usb tablet Michael Tokarev
2010-09-10 11:47 ` Jes Sorensen
2010-09-10 12:16 ` Michael Tokarev
2010-09-10 16:17 ` high load with usb device Michael Tokarev
2010-09-12 9:26 ` Avi Kivity
2010-09-14 6:51 ` Michael Tokarev
2010-09-14 9:06 ` Avi Kivity
2010-09-14 9:08 ` Avi Kivity
2010-09-14 10:00 ` Michael Tokarev
2010-09-14 10:07 ` Avi Kivity
2010-09-14 10:25 ` Michael Tokarev
2010-09-14 10:39 ` Avi Kivity
2010-09-14 11:02 ` Michael Tokarev
2010-09-14 13:15 ` Michael Tokarev
2010-09-14 13:25 ` Avi Kivity
2010-09-14 13:29 ` Michael Tokarev
2010-09-14 13:38 ` Michael Tokarev
2010-09-14 14:45 ` Avi Kivity
2010-09-14 14:53 ` Michael Tokarev
2010-09-14 16:00 ` Avi Kivity
2010-09-14 16:29 ` Michael Tokarev
2010-09-14 16:37 ` Avi Kivity
2010-09-14 16:50 ` Michael Tokarev
2010-09-14 16:45 ` David S. Ahern
2010-09-14 15:51 ` David S. Ahern
2010-09-14 16:00 ` Michael Tokarev
2010-09-14 16:09 ` David S. Ahern
2010-09-10 12:19 ` high load with win7 & usb tablet Avi Kivity
2010-09-10 12:44 ` Michael Tokarev
2010-09-10 12:50 ` Avi Kivity [this message]
[not found] ` <4C8A44E6.2060008@msgid.tls.msk.ru>
2010-09-10 14:56 ` Avi Kivity
2010-09-10 15:03 ` Michael Tokarev
2010-09-10 16:03 ` Avi Kivity
2010-09-14 8:26 ` Brad Campbell
2010-09-14 8:33 ` Michael Tokarev
2010-09-14 8:46 ` Brad Campbell
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=4C8A29A6.60108@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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