From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=34775 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OOtpB-0006hy-31
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 10:42:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <pbonzini@redhat.com>) id 1OOtp9-0004FD-Sc
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 10:42:40 -0400
Received: from mx1.redhat.com ([209.132.183.28]:39995)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <pbonzini@redhat.com>) id 1OOtp9-0004F0-KU
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 10:42:39 -0400
Message-ID: <4C18E2D5.3050301@redhat.com>
Date: Wed, 16 Jun 2010 16:42:29 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <20100616115404.10988.62371.stgit@localhost.localdomain>
	<20100616115651.10988.91292.stgit@localhost.localdomain>
	<4C18E266.2030800@linux.vnet.ibm.com>
In-Reply-To: <4C18E266.2030800@linux.vnet.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH V4 1/3] qemu: Add qemu-barrier support to
 qemu-thread framework.
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Avi Kivity <avi@redhat.com>, Qemu-development List <qemu-devel@nongnu.org>, Corentin Chary <corentin.chary@gmail.com>, Gautham R Shenoy <ego@in.ibm.com>

On 06/16/2010 04:40 PM, Anthony Liguori wrote:
> On 06/16/2010 06:56 AM, Gautham R Shenoy wrote:
>> Signed-off-by: Gautham R Shenoy<ego@in.ibm.com>
>
> I don't see barrier being used and I don't think it ought to be used.
> threadlets are meant provide a means to execute a synchronous function
> asynchronously. It should never be necessary to synchronize threadlets
> using a barrier.

It's used for flush_threadlet_queue.

Paolo