mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@kernel.org>
To: Bang Li <libang.linuxer@gmail.com>, vgupta@kernel.org
Cc: peterz@infradead.org, mingo@kernel.org,
	valentin.schneider@arm.com, linux-snps-arc@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARC: remove redundant READ_ONCE() in cmpxchg loop
Date: Mon, 18 Apr 2022 12:19:53 -0700	[thread overview]
Message-ID: <e86916c4-1a5c-f89d-bcec-c4ed275aa4be@kernel.org> (raw)
In-Reply-To: <20220319020316.142479-1-libang.linuxer@gmail.com>



On 3/18/22 19:03, Bang Li wrote:
> This patch reverts commit 7082a29c22ac ("ARC: use ACCESS_ONCE in cmpxchg
> loop").
>
> It is not necessary to use READ_ONCE() because cmpxchg contains barrier. We
> can get it from commit d57f727264f1 ("ARC: add compiler barrier to LLSC
> based cmpxchg").
>
> Signed-off-by: Bang Li <libang.linuxer@gmail.com>

Indeed this is not needed. However have you checked the code with and/wo 
this change to see if it builds the same.

-Vineet

> ---
>   arch/arc/kernel/smp.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arc/kernel/smp.c b/arch/arc/kernel/smp.c
> index 78e6d069b1c1..56c23f3e1309 100644
> --- a/arch/arc/kernel/smp.c
> +++ b/arch/arc/kernel/smp.c
> @@ -274,7 +274,7 @@ static void ipi_send_msg_one(int cpu, enum ipi_msg_type msg)
>   	 * and read back old value
>   	 */
>   	do {
> -		new = old = READ_ONCE(*ipi_data_ptr);
> +		new = old = *ipi_data_ptr;
>   		new |= 1U << msg;
>   	} while (cmpxchg(ipi_data_ptr, old, new) != old);
>   


      reply	other threads:[~2022-04-18 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19  2:03 Bang Li
2022-04-18 19:19 ` Vineet Gupta [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=e86916c4-1a5c-f89d-bcec-c4ed275aa4be@kernel.org \
    --to=vgupta@kernel.org \
    --cc=libang.linuxer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=valentin.schneider@arm.com \
    /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

all inboxes | Powered by JetHome®