On Wed, Mar 2, 2011 at 10:39 AM, ya su wrote:
> io_thread bt as the following:
> #0 0x7f3086eaa034 in __lll_lock_wait () from /lib64/libpthread.so.0
> #1 0x7f3086ea5345 in _L_lock_870 () from /lib64/libpthread.so.0
> #2 0x7f3086ea5217 in pthread_mutex_lock () from /lib64/libpthread.
hi,all:
io_thread bt as the following:
#0 0x7f3086eaa034 in __lll_lock_wait () from /lib64/libpthread.so.0
#1 0x7f3086ea5345 in _L_lock_870 () from /lib64/libpthread.so.0
#2 0x7f3086ea5217 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3 0x00436018 in kvm_mutex_lock
On 03/01/2011 05:01 PM, Stefan Hajnoczi wrote:
On Tue, Mar 1, 2011 at 12:39 PM, ya su wrote:
> how about to remove kvm_handle_io/handle_mmio in kvm_run function
> into kvm_main_loop, as these operation belong to io operation, this
> will remove the qemu_mutux between the 2 threads. is thi
On Tue, Mar 1, 2011 at 12:39 PM, ya su wrote:
> how about to remove kvm_handle_io/handle_mmio in kvm_run function
> into kvm_main_loop, as these operation belong to io operation, this
> will remove the qemu_mutux between the 2 threads. is this an
> reasonable thought?
>
> In order to keep th
first say sorry for the same mail sent more than one time, I don't
know it will take so long time to come back.
hi, stefan:
thank for your explaining.
how about to remove kvm_handle_io/handle_mmio in kvm_run function
into kvm_main_loop, as these operation belong to io operation, this
wil
On Tue, Mar 1, 2011 at 5:01 AM, ya su wrote:
> kvm start with disk image on nfs server, when nfs server can not be
> reached, monitor will be blocked. I change io_thread to SCHED_RR
> policy, it will work unfluently waiting for disk read/write timeout.
There are some synchronous disk image read
hi all:
kvm start with disk image on nfs server, when nfs server can not be
reached, monitor will be blocked. I change io_thread to SCHED_RR
policy, it will work unfluently waiting for disk read/write timeout.
I have tested a standalone thread to process kvm_handle_io, it can not
start up corr
, monitor will still be blocked by read/write
disk request.
is there anyone that will have a good suggestion? thanks.
Green.
-- Forwarded message --
From: ya su
Date: 2011/2/28
Subject: problem about blocked monitor when disk image on NFS can not
be reached.
To: kvm@vger.kernel.org
hi:
kvm start with disk image on nfs server, when nfs server can not be
reached, monitor will be blocked. I change io_thread to SCHED_RR
policy, it will work unfluently waiting for disk read/write timeout.
I think one solution to this is to change kvm_handle_io in a
seperate thread, I will p
