From: Mark Burton <mark.burton@greensocs.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: mttcg@listserver.greensocs.com,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alexander Graf" <agraf@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Guillaume Delbergue" <guillaume.delbergue@greensocs.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Use atomic cmpxchg to atomically check the exclusive value in a STREX
Date: Tue, 9 Jun 2015 16:02:06 +0200 [thread overview]
Message-ID: <0860533C-AC27-4A7B-ABDA-9333A2FB7B7F@greensocs.com> (raw)
In-Reply-To: <87oakp6kzl.fsf@linaro.org>
> On 9 Jun 2015, at 15:59, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> fred.konrad@greensocs.com writes:
>
>> From: KONRAD Frederic <fred.konrad@greensocs.com>
>>
<snip>
>> +DEF_HELPER_4(atomic_cmpxchg64, i32, env, i32, i64, i32)
>> +DEF_HELPER_2(atomic_check, i32, env, i32)
>> +DEF_HELPER_1(atomic_release, void, env)
>
> Apologies for being split over several mails, I didn't notice before
No problem - personally prefer to keep the threads separate.
> that atomic_check/release don't seem to be called at all in this patch.
> Is there later work that uses it?
I suspect that this is just a case of not cleaning up- I think we used check and release, and then ditched them… I’ll check (and release :-) )
Cheers
Mark.
prev parent reply other threads:[~2015-06-09 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 14:31 [Qemu-devel] [RFC PATCH] Use atomic cmpxchg to atomically check the exclusive value in a STREX fred.konrad
2015-06-09 9:12 ` Alex Bennée
2015-06-09 9:39 ` Mark Burton
2015-06-09 13:55 ` Alex Bennée
2015-06-09 14:00 ` Mark Burton
2015-06-09 15:35 ` Alex Bennée
2015-06-10 8:03 ` Frederic Konrad
2015-06-10 8:41 ` Frederic Konrad
2015-06-09 13:59 ` Alex Bennée
2015-06-09 14:02 ` Mark Burton [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=0860533C-AC27-4A7B-ABDA-9333A2FB7B7F@greensocs.com \
--to=mark.burton@greensocs.com \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=fred.konrad@greensocs.com \
--cc=guillaume.delbergue@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).