On 2012-06-23 00:56, Anthony Liguori wrote:
On 06/22/2012 05:27 PM, Jan Kiszka wrote:
On 2012-06-22 23:44, Anthony Liguori wrote:
1) unlock iothread before entering the do {} look in kvm_cpu_exec()
a) reacquire the lock after the loop
b) reacquire the lock in kvm_handle_io()
c)
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2012-06-21 16:49, Liu Ping Fan wrote:
Nowadays, we use qemu_mutex_lock_iothread()/qemu_mutex_unlock_iothread() to
protect the race to access the emulated dev launched by vcpu threads
iothread.
But this lock is
On 2012-06-22 12:24, liu ping fan wrote:
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2012-06-21 16:49, Liu Ping Fan wrote:
Nowadays, we use qemu_mutex_lock_iothread()/qemu_mutex_unlock_iothread() to
protect the race to access the emulated dev launched by vcpu
On 06/22/2012 05:37 AM, Jan Kiszka wrote:
On 2012-06-22 12:24, liu ping fan wrote:
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszkajan.kis...@siemens.com wrote:
On 2012-06-21 16:49, Liu Ping Fan wrote:
Nowadays, we use qemu_mutex_lock_iothread()/qemu_mutex_unlock_iothread() to
protect the race
On 2012-06-22 22:11, Anthony Liguori wrote:
On 06/22/2012 05:37 AM, Jan Kiszka wrote:
On 2012-06-22 12:24, liu ping fan wrote:
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszkajan.kis...@siemens.com
wrote:
On 2012-06-21 16:49, Liu Ping Fan wrote:
Nowadays, we use
On 06/22/2012 04:14 PM, Jan Kiszka wrote:
On 2012-06-22 22:11, Anthony Liguori wrote:
On 06/22/2012 05:37 AM, Jan Kiszka wrote:
On 2012-06-22 12:24, liu ping fan wrote:
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszkajan.kis...@siemens.com
wrote:
On 2012-06-21 16:49, Liu Ping Fan wrote:
On 2012-06-22 23:44, Anthony Liguori wrote:
On 06/22/2012 04:14 PM, Jan Kiszka wrote:
On 2012-06-22 22:11, Anthony Liguori wrote:
On 06/22/2012 05:37 AM, Jan Kiszka wrote:
On 2012-06-22 12:24, liu ping fan wrote:
On Thu, Jun 21, 2012 at 11:23 PM, Jan Kiszkajan.kis...@siemens.com
wrote:
On
On 06/22/2012 05:27 PM, Jan Kiszka wrote:
On 2012-06-22 23:44, Anthony Liguori wrote:
1) unlock iothread before entering the do {} look in kvm_cpu_exec()
a) reacquire the lock after the loop
b) reacquire the lock in kvm_handle_io()
c) introduce an unlocked memory accessor that for
Nowadays, we use qemu_mutex_lock_iothread()/qemu_mutex_unlock_iothread() to
protect the race to access the emulated dev launched by vcpu threads iothread.
But this lock is too big. We can break it down.
These patches separate the CPUArchState's protection from the other devices, so
we
can have
On 2012-06-21 16:49, Liu Ping Fan wrote:
Nowadays, we use qemu_mutex_lock_iothread()/qemu_mutex_unlock_iothread() to
protect the race to access the emulated dev launched by vcpu threads
iothread.
But this lock is too big. We can break it down.
These patches separate the CPUArchState's
10 matches
Mail list logo
