[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [s390] possible deadlock in handle_sigp? |
Date: |
Mon, 12 Sep 2016 20:03:10 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
On 12/09/2016 19:37, Christian Borntraeger wrote:
> On 09/12/2016 06:44 PM, Paolo Bonzini wrote:
> > I think that two CPUs doing reciprocal SIGPs could in principle end up
> > waiting on each other to complete their run_on_cpu. If the SIGP has to
> > be synchronous the fix is not trivial (you'd have to put the CPU in a
> > state similar to cpu->halted = 1), otherwise it's enough to replace
> > run_on_cpu with async_run_on_cpu.
>
> IIRC the sigps are supossed to be serialized by the big QEMU lock. WIll
> have a look.
Yes, but run_on_cpu drops it when it waits on the qemu_work_cond
condition variable. (Related: I stumbled upon it because I wanted to
remove the BQL from run_on_cpu work items).
Paolo
- [Qemu-devel] [s390] possible deadlock in handle_sigp?, Paolo Bonzini, 2016/09/12
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, Christian Borntraeger, 2016/09/12
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?,
Paolo Bonzini <=
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, Christian Borntraeger, 2016/09/13
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, David Hildenbrand, 2016/09/15
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, Paolo Bonzini, 2016/09/15
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, Christian Borntraeger, 2016/09/19
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, David Hildenbrand, 2016/09/19
- Re: [Qemu-devel] [s390] possible deadlock in handle_sigp?, Christian Borntraeger, 2016/09/19
[Qemu-devel] [PATCH] s390x/kvm: Fix potential deadlock in sigp handling, Christian Borntraeger, 2016/09/20