From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48483)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bobby.prani@gmail.com>) id 1bA0Ci-0005uJ-GJ
	for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:28:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bobby.prani@gmail.com>) id 1bA0Cg-0005IW-PA
	for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:28:51 -0400
Received: from mail-io0-x22d.google.com ([2607:f8b0:4001:c06::22d]:36847)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bobby.prani@gmail.com>) id 1bA0Cg-0005IS-KA
	for qemu-devel@nongnu.org; Mon, 06 Jun 2016 15:28:50 -0400
Received: by mail-io0-x22d.google.com with SMTP id n127so25926396iof.3
	for <qemu-devel@nongnu.org>; Mon, 06 Jun 2016 12:28:50 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <f1ce9d83-720b-f0d2-b11f-da58f9bc8fa4@twiddle.net>
References: <20160531183928.29406-1-bobby.prani@gmail.com>
	<20160531183928.29406-2-bobby.prani@gmail.com>
	<57505F1A.3020808@gmail.com>
	<68c32d50-adc2-25b2-b136-2a486f6b3de7@twiddle.net>
	<5750995D.6030005@gmail.com>
	<8e9b8569-89a5-845a-a856-7f2fa4435659@twiddle.net>
	<CAJhHMCDEHkpcs0nk_CaBWphLkvsRtNDqDGkAiuSGSopVJqwPPw@mail.gmail.com>
	<57559A66.6040408@gmail.com>
	<CAJhHMCCPcTdAWcthP2HUFdwSHjgZoffKWg48vUP802wxVDXYTA@mail.gmail.com>
	<57559B93.7090003@gmail.com>
	<CAJhHMCBqyPC5T17T+wsCeRmZxPXCBtrV16pOQs144yM7g7ffYg@mail.gmail.com>
	<5755A164.9040709@gmail.com>
	<CAJhHMCD=KrnVrhMdHwgrZZmgG8FPuvr72uRrcCNzA9-A89v9yQ@mail.gmail.com>
	<f1ce9d83-720b-f0d2-b11f-da58f9bc8fa4@twiddle.net>
From: Pranith Kumar <bobby.prani@gmail.com>
Date: Mon, 6 Jun 2016 15:28:20 -0400
Message-ID: <CAJhHMCBOszH12BpE4AJGwY3ZH4DevS2nFiCQR-R-UadMSOnb2Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [RFC v2 PATCH 01/13] Introduce TCGOpcode for
 memory barrier
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Richard Henderson <rth@twiddle.net>
Cc: Sergey Fedorov <serge.fdrv@gmail.com>, "open list:All patches CC here" <qemu-devel@nongnu.org>, =?UTF-8?B?QWxleCBCZW5uw6ll?= <alex.bennee@linaro.org>

On Mon, Jun 6, 2016 at 3:23 PM, Richard Henderson <rth@twiddle.net> wrote:
> On 06/06/2016 10:11 AM, Pranith Kumar wrote:
>>
>> If I read it correctly TCG_BAR_SYNC is equivalent to OR of all the
>> other four barriers. I am not sure if we can just construct SYNC like
>> this or if we need to define it explicitly though.
>
>
> AFAICS, sparc membar #sync is stronger.

I tried looking it up but it's not clear. How is it stronger? And do
we need those strong guarantees in our front-end/back-end?

Thanks,
-- 
Pranith