From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Dor Laor <dor.laor@gmail.com>, kvm-devel@lists.sourceforge.net
Subject: Re: [patch 0/3] separate thread for IO handling V3
Date: Thu, 03 Apr 2008 18:26:17 +0300 [thread overview]
Message-ID: <47F4F719.8040703@qumranet.com> (raw)
In-Reply-To: <47F4D1BA.8060604@qumranet.com>
Avi Kivity wrote:
> Avi Kivity wrote:
>>
>> There's still something wrong. When I start Windows with these
>> patches applied, Windows startup consumes ~50 sec of cpu time,
>> compared to ~12 sec without. Pinning qemu into cpu 0 seems to fix this.
>>
>> I'll investigate some more.
>>
>
> Changing GUI_REFRESH_INTERVAL to 1000 (from 30) reduces cpu usage back
> to normal. So I'm guessing there's some bad interaction between the
> iothread getting the dirty log and vcpu 0.
>
Turns out we held slots_lock while in guest mode (which we can be in for
unbounded time). Dropping the lock restored behavior to normal, so I'm
applying the patches.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
prev parent reply other threads:[~2008-04-03 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 23:20 [patch 0/3] separate thread for IO handling V3 Marcelo Tosatti
2008-04-02 23:20 ` [patch 1/3] QEMU/KVM: separate thread for IO handling Marcelo Tosatti
2008-04-02 23:20 ` [patch 2/3] QEMU/KVM: add function to handle signals Marcelo Tosatti
2008-04-02 23:20 ` [patch 3/3] QEMU/KVM: notify IO thread of pending bhs Marcelo Tosatti
2008-04-03 10:24 ` [patch 0/3] separate thread for IO handling V3 Avi Kivity
2008-04-03 12:46 ` Avi Kivity
2008-04-03 15:26 ` Avi Kivity [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=47F4F719.8040703@qumranet.com \
--to=avi@qumranet.com \
--cc=dor.laor@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.