From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Burton <paul.burton@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Huacai Chen <chenhc@lemote.com>, Huang Pei <huangpei@loongson.cn>
Subject: Re: linux-next: manual merge of the mips tree with the mips-fixes tree
Date: Wed, 6 Feb 2019 10:44:33 +1100 [thread overview]
Message-ID: <20190206104433.1c832a0b@canb.auug.org.au> (raw)
In-Reply-To: <20190205233530.tnk6boxzxm7okgcr@pburton-laptop>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Hi Paul,
On Tue, 5 Feb 2019 23:35:31 +0000 Paul Burton <paul.burton@mips.com> wrote:
>
> cmpxchg() doesn't need the added loongson_llsc_mb() barrier that
> set_pte() has in mips-fixes because for the affected Loongson 3
> configurations the smp_mb__before_llsc() that cmpxchg() already contains
> is equivalent (both will emit a "sync 0" instruction).
OK, good to know, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-05 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 22:17 linux-next: manual merge of the mips tree with the mips-fixes tree Stephen Rothwell
2019-02-05 23:35 ` Paul Burton
2019-02-05 23:44 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-04 23:05 Stephen Rothwell
2019-02-07 22:22 Stephen Rothwell
2018-06-28 23:46 Stephen Rothwell
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=20190206104433.1c832a0b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chenhc@lemote.com \
--cc=huangpei@loongson.cn \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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