From: James Hogan <james.hogan@mips.com>
To: Joshua Kinard <kumba@gentoo.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>
Subject: Re: Question regarding atomic ops
Date: Wed, 25 Oct 2017 08:59:04 +0100 [thread overview]
Message-ID: <20171025075903.GA15260@jhogan-linux> (raw)
In-Reply-To: <f25e53f7-d25d-e9d8-f592-d94e988da28e@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Mon, Oct 16, 2017 at 01:51:01AM -0400, Joshua Kinard wrote:
> The only uncertainty I have is the bottom of atomic_sub_if_positive and
> atomic64_sub_if_positive. In R10000_LLSC_WAR case, the end of the assembler is:
>
> "+" GCC_OFF_SMALL_ASM() (v->counter)
> : "Ir" (i), GCC_OFF_SMALL_ASM() (v->counter)
The GCC_OFF_SMALL_ASM() (v->counter) input here looks redundant because
1) the output one has +, which means input and output
2) %4 is never referenced.
> : "memory");
To me this appears to be redundant since the only side effects are
writing to v->counter which is already an output, and in any case the
smp_mb__before_llsc() and smp_llsc_mb() imply memory clobber anyway.
>
> While the standard case is:
>
> : "=&r" (result), "=&r" (temp),
> "+" GCC_OFF_SMALL_ASM() (v->counter)
> : "Ir" (i));
So yeh, I'd go for this unless anybody can think of a reason it wouldn't
work in the R10000_LLSC_WAR case.
Hope that helps.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@mips.com>
To: Joshua Kinard <kumba@gentoo.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Question regarding atomic ops
Date: Wed, 25 Oct 2017 08:59:04 +0100 [thread overview]
Message-ID: <20171025075903.GA15260@jhogan-linux> (raw)
Message-ID: <20171025075904.hWv9cciPLOuGpJv6rAe2tZ17izsDY-SyeUWTgM8D5l0@z> (raw)
In-Reply-To: <f25e53f7-d25d-e9d8-f592-d94e988da28e@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Mon, Oct 16, 2017 at 01:51:01AM -0400, Joshua Kinard wrote:
> The only uncertainty I have is the bottom of atomic_sub_if_positive and
> atomic64_sub_if_positive. In R10000_LLSC_WAR case, the end of the assembler is:
>
> "+" GCC_OFF_SMALL_ASM() (v->counter)
> : "Ir" (i), GCC_OFF_SMALL_ASM() (v->counter)
The GCC_OFF_SMALL_ASM() (v->counter) input here looks redundant because
1) the output one has +, which means input and output
2) %4 is never referenced.
> : "memory");
To me this appears to be redundant since the only side effects are
writing to v->counter which is already an output, and in any case the
smp_mb__before_llsc() and smp_llsc_mb() imply memory clobber anyway.
>
> While the standard case is:
>
> : "=&r" (result), "=&r" (temp),
> "+" GCC_OFF_SMALL_ASM() (v->counter)
> : "Ir" (i));
So yeh, I'd go for this unless anybody can think of a reason it wouldn't
work in the R10000_LLSC_WAR case.
Hope that helps.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-25 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 2:24 Question regarding atomic ops Joshua Kinard
2017-10-10 2:34 ` Joshua Kinard
2017-10-10 14:23 ` Ralf Baechle
2017-10-11 13:15 ` Joshua Kinard
2017-10-11 13:15 ` Joshua Kinard
2017-10-16 5:51 ` Joshua Kinard
2017-10-25 7:59 ` James Hogan [this message]
2017-10-25 7:59 ` James Hogan
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=20171025075903.GA15260@jhogan-linux \
--to=james.hogan@mips.com \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--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