From: Marco Elver <elver@google.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Dmitry Vyukov <dvyukov@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kasan-dev@googlegroups.com, Rohan McLure <rmclure@linux.ibm.com>
Subject: Re: [PATCH 0/3] Extend KCSAN to all powerpc
Date: Fri, 12 May 2023 18:22:32 +0200 [thread overview]
Message-ID: <CANpmjNNLaA6TQnjwfhwd_=4o6S14vX5AAm4Az_bDaCb7zgNO_w@mail.gmail.com> (raw)
In-Reply-To: <cover.1683892665.git.christophe.leroy@csgroup.eu>
On Fri, 12 May 2023 at 17:31, Christophe Leroy
<christophe.leroy@csgroup.eu> wrote:
>
> This series enables KCSAN on all powerpc.
>
> To do this, a fix is required to KCSAN core.
>
> Once that fix is done, the stubs can also be removed from xtensa.
>
> It would be nice if patch 1 could go in v6.4 as a fix, then patches 2 and 3
> could be handled separately in each architecture in next cycle.
>
> Christophe Leroy (2):
> kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures
> xtensa: Remove 64 bits atomic builtins stubs
>
> Rohan McLure (1):
> powerpc/{32,book3e}: kcsan: Extend KCSAN Support
Acked-by: Marco Elver <elver@google.com>
WARNING: multiple messages have this Message-ID (diff)
From: Marco Elver <elver@google.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Chris Zankel <chris@zankel.net>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Rohan McLure <rmclure@linux.ibm.com>,
kasan-dev@googlegroups.com, linuxppc-dev@lists.ozlabs.org,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH 0/3] Extend KCSAN to all powerpc
Date: Fri, 12 May 2023 18:22:32 +0200 [thread overview]
Message-ID: <CANpmjNNLaA6TQnjwfhwd_=4o6S14vX5AAm4Az_bDaCb7zgNO_w@mail.gmail.com> (raw)
In-Reply-To: <cover.1683892665.git.christophe.leroy@csgroup.eu>
On Fri, 12 May 2023 at 17:31, Christophe Leroy
<christophe.leroy@csgroup.eu> wrote:
>
> This series enables KCSAN on all powerpc.
>
> To do this, a fix is required to KCSAN core.
>
> Once that fix is done, the stubs can also be removed from xtensa.
>
> It would be nice if patch 1 could go in v6.4 as a fix, then patches 2 and 3
> could be handled separately in each architecture in next cycle.
>
> Christophe Leroy (2):
> kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures
> xtensa: Remove 64 bits atomic builtins stubs
>
> Rohan McLure (1):
> powerpc/{32,book3e}: kcsan: Extend KCSAN Support
Acked-by: Marco Elver <elver@google.com>
next prev parent reply other threads:[~2023-05-12 16:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:31 [PATCH 0/3] Extend KCSAN to all powerpc Christophe Leroy
2023-05-12 15:31 ` Christophe Leroy
2023-05-12 15:31 ` [PATCH 1/3] kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures Christophe Leroy
2023-05-12 15:31 ` Christophe Leroy
2023-05-12 16:09 ` Marco Elver
2023-05-12 16:09 ` Marco Elver
2023-05-12 18:39 ` Christophe Leroy
2023-05-12 18:39 ` Christophe Leroy
2023-06-09 12:55 ` Michael Ellerman
2023-06-09 12:55 ` Michael Ellerman
2023-05-12 15:31 ` [PATCH 2/3] powerpc/{32,book3e}: kcsan: Extend KCSAN Support Christophe Leroy
2023-05-12 15:31 ` Christophe Leroy
2023-05-12 15:31 ` [PATCH 3/3] xtensa: Remove 64 bits atomic builtins stubs Christophe Leroy
2023-05-12 15:31 ` Christophe Leroy
2023-05-12 16:38 ` Max Filippov
2023-05-12 16:38 ` Max Filippov
2023-05-12 16:22 ` Marco Elver [this message]
2023-05-12 16:22 ` [PATCH 0/3] Extend KCSAN to all powerpc Marco Elver
2023-07-03 5:26 ` Michael Ellerman
2023-07-03 5:26 ` Michael Ellerman
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='CANpmjNNLaA6TQnjwfhwd_=4o6S14vX5AAm4Az_bDaCb7zgNO_w@mail.gmail.com' \
--to=elver@google.com \
--cc=chris@zankel.net \
--cc=christophe.leroy@csgroup.eu \
--cc=dvyukov@google.com \
--cc=jcmvbkbc@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=rmclure@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.