public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail•com>
To: "Rohan McLure" <rmclure@linux•ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists•ozlabs.org>, arnd@arndb•de
Subject: Re: [PATCH 03/12] powerpc: qspinlock: Enforce qnode writes prior to publishing to queue
Date: Tue, 09 May 2023 16:45:22 +1000	[thread overview]
Message-ID: <CSHJLY451TDZ.RF0HOE2T64GT@wheely> (raw)
In-Reply-To: <46600B7B-1E59-4B82-82DF-27D3B0473EEF@linux.ibm.com>

On Tue May 9, 2023 at 3:26 PM AEST, Rohan McLure wrote:
> > On 9 May 2023, at 12:04 pm, Nicholas Piggin <npiggin@gmail•com> wrote:
> > 
> > On Mon May 8, 2023 at 12:01 PM AEST, Rohan McLure wrote:
> >> Use a compiler barrier to enforce that all fields of a new struct qnode
> >> be written to (especially the lock value) before publishing the qnode to
> >> the waitqueue.
> > 
> > publish_tail_cpu is the release barrier for this and includes the memory
> > clobber there. Can we annotate that instead?
>
> Got it, I see that one now.
>
> On another note though, it looks like the memory clobber doesn’t serve
> to squash KCSAN warnings here.

Aha, publish_tail_cpu() needs a kcsan_release().

Thanks,
Nick

  reply	other threads:[~2023-05-09  6:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  2:01 [PATCH 00/12] powerpc: KCSAN fix warnings and mark accesses Rohan McLure
2023-05-08  2:01 ` [PATCH 01/12] powerpc: qspinlock: Fix qnode->locked value interpretation Rohan McLure
2023-05-09  2:01   ` Nicholas Piggin
2023-05-09  4:26     ` Rohan McLure
2023-05-08  2:01 ` [PATCH 02/12] powerpc: qspinlock: Mark accesses to qnode lock checks Rohan McLure
2023-05-09  2:02   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 03/12] powerpc: qspinlock: Enforce qnode writes prior to publishing to queue Rohan McLure
2023-05-09  2:04   ` Nicholas Piggin
2023-05-09  5:26     ` Rohan McLure
2023-05-09  6:45       ` Nicholas Piggin [this message]
2023-05-08  2:01 ` [PATCH 04/12] asm-generic/mmiowb: Mark accesses to fix KCSAN warnings Rohan McLure
2023-05-08  6:30   ` Arnd Bergmann
2023-05-08 15:44   ` [PATCH 4/12] " Gautam Menghani
2023-05-09  2:16   ` [PATCH 04/12] " Nicholas Piggin
2023-05-08  2:01 ` [PATCH 05/12] powerpc: Mark [h]ssr_valid accesses in check_return_regs_valid Rohan McLure
2023-05-09  2:17   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 06/12] powerpc: Mark accesses to power_save callback in arch_cpu_idle Rohan McLure
2023-05-09  2:21   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 07/12] powerpc: powernv: Fix KCSAN datarace warnings on idle_state contention Rohan McLure
2023-05-09  2:26   ` Nicholas Piggin
2023-05-10  2:00     ` Rohan McLure
2023-05-08  2:01 ` [PATCH 08/12] powerpc: Annotate accesses to ipi message flags Rohan McLure
2023-05-09  2:28   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 09/12] powerpc: Mark writes registering ipi to host cpu through kvm Rohan McLure
2023-05-09  2:30   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 10/12] powerpc: powernv: Annotate data races in opal events Rohan McLure
2023-05-09  2:31   ` Nicholas Piggin
2023-05-08  2:01 ` [PATCH 11/12] powerpc: powernv: Annotate asynchronous access to opal tokens Rohan McLure
2023-05-08  2:01 ` [PATCH 12/12] powerpc: Mark asynchronous accesses to irq_data Rohan McLure

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=CSHJLY451TDZ.RF0HOE2T64GT@wheely \
    --to=npiggin@gmail$(echo .)com \
    --cc=arnd@arndb$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=rmclure@linux$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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