From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Aurelien Jarno <aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-commits] kvm: qemu: consume all signals available in order to reduce latency
Date: Sun, 22 Jul 2007 16:52:56 +0300 [thread overview]
Message-ID: <46A36138.4000408@qumranet.com> (raw)
In-Reply-To: <46A35F46.8040002-rXXEIb44qovR7s880joybQ@public.gmane.org>
Aurelien Jarno wrote:
>
>> }
>> /*
>> * we call select() even if no signal was received, to account for
>> * for which there is no signal handler installed.
>> */
>> + pthread_mutex_unlock(&qemu_mutex);
>> + cpu_single_env = vcpu_env;
>> main_loop_wait(0);
>> pthread_mutex_unlock(&qemu_mutex);
>> }
>>
>
> The SMP problems comes from here. The first one should probably be
> pthread_mutex_lock and not pthread_mutex_unlock.
>
>
Duh! Thanks for saving me potentially hours of debugging time.
Really, someone who's more careful about testing should be doing this thing.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-07-22 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070722102812.417CB250135@il.qumranet.com>
[not found] ` <20070722102812.417CB250135-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-07-22 13:44 ` [kvm-commits] kvm: qemu: consume all signals available in order to reduce latency Aurelien Jarno
[not found] ` <46A35F46.8040002-rXXEIb44qovR7s880joybQ@public.gmane.org>
2007-07-22 13:52 ` 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=46A36138.4000408@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.