All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ipmi: do not take/drop iothread lock
Date: Tue, 26 Jan 2016 11:57:02 -0600	[thread overview]
Message-ID: <56A7B36E.9070409@mvista.com> (raw)
In-Reply-To: <20160126182054-mutt-send-email-mst@redhat.com>

On 01/26/2016 10:21 AM, Michael S. Tsirkin wrote:
> On Tue, Jan 26, 2016 at 05:15:53PM +0100, Paolo Bonzini wrote:
>> This is not necessary and actually causes a hang; it was probably copied
>> and pasted from KVM code, that is one of the very few places that run
>> outside iothread lock.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Makes sense. I wonder how hard would it be to have a test to catch this.

The IPMI side would be easy for me, but I don't know how to handle 
catching the NMI.

-corey

>> ---
>>   hw/ipmi/ipmi.c | 2 --
>>   1 file changed, 2 deletions(-)
>>
>> diff --git a/hw/ipmi/ipmi.c b/hw/ipmi/ipmi.c
>> index 52aba1e..fcba0ca 100644
>> --- a/hw/ipmi/ipmi.c
>> +++ b/hw/ipmi/ipmi.c
>> @@ -50,9 +50,7 @@ static int ipmi_do_hw_op(IPMIInterface *s, enum ipmi_op op, int checkonly)
>>           if (checkonly) {
>>               return 0;
>>           }
>> -        qemu_mutex_lock_iothread();
>>           qmp_inject_nmi(NULL);
>> -        qemu_mutex_unlock_iothread();
>>           return 0;
>>   
>>       case IPMI_POWERCYCLE_CHASSIS:
>> -- 
>> 2.5.0

  reply	other threads:[~2016-01-26 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 16:15 [Qemu-devel] [PATCH] ipmi: do not take/drop iothread lock Paolo Bonzini
2016-01-26 16:21 ` Michael S. Tsirkin
2016-01-26 17:57   ` Corey Minyard [this message]
2016-01-26 18:00     ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2016-01-26 16:59 Paolo Bonzini

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=56A7B36E.9070409@mvista.com \
    --to=cminyard@mvista.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.