From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 00/12] atomics: generate atomic headers / instrument arm64
Date: Sat, 14 Jul 2018 15:01:30 +0200 [thread overview]
Message-ID: <20180714130130.GA23906@gmail.com> (raw)
In-Reply-To: <20180713150607.rf6hkwsxpe4gsxqt@lakrids.cambridge.arm.com>
* Mark Rutland <mark.rutland@arm.com> wrote:
> On Fri, Jul 06, 2018 at 03:21:24PM +0200, Peter Zijlstra wrote:
> > On Fri, Jul 06, 2018 at 02:16:04PM +0100, Will Deacon wrote:
> > > On Thu, Jul 05, 2018 at 05:40:41PM +0100, Mark Rutland wrote:
> > > > This series scripts the generation of the various atomic headers, to ensure
> > > > that the various atomic APIs remain consistent, reducing the risk of human
> > > > error, and simplifying future rework. This fleshes out the instrumented atomics
> > > > such that arm64 can be migrated over to them.
> > >
> > > Thanks! For the series apart from the shell scripts:
> > >
> > > Acked-by: Will Deacon <will.deacon@arm.com>
> >
> > Awesome, Ingo can you stuff these here patches into locking/core
> > someplace?
>
> Looks like Ingo was only Cc'd for the above.
>
> Ingo, are you happy to pick these up?
>
> I've pushed out a branch [1] with Will's acks and a trivial commit
> message change for patches 8-10 which I don't think is too important. I
> can post that as v4 if you'd prefer to pick that.
Yeah, please post the very latest to the mailing list.
Thanks!
Ingo
prev parent reply other threads:[~2018-07-14 13:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 16:40 [PATCHv3 00/12] atomics: generate atomic headers / instrument arm64 Mark Rutland
2018-07-05 16:40 ` [PATCHv3 01/12] atomic/tty: Fix up atomic abuse in ldsem Mark Rutland
2018-07-05 16:40 ` [PATCHv3 02/12] atomics/x86: reduce arch_cmpxchg64*() instrumentation Mark Rutland
2018-07-05 16:40 ` [PATCHv3 03/12] atomics: simplify cmpxchg() instrumentation Mark Rutland
2018-07-05 16:40 ` [PATCHv3 04/12] atomics/treewide: instrument xchg() Mark Rutland
2018-07-05 16:40 ` [PATCHv3 05/12] atomics: instrument cmpxchg_double*() Mark Rutland
2018-07-05 16:40 ` [PATCHv3 06/12] atomics/treewide: rework ordering barriers Mark Rutland
2018-07-05 16:40 ` [PATCHv3 07/12] atomics: add common header generation files Mark Rutland
2018-07-05 16:40 ` [PATCHv3 08/12] atomics: switch to generated fallbacks Mark Rutland
2018-07-05 17:23 ` Peter Zijlstra
2018-07-06 5:51 ` Mark Rutland
2018-07-05 16:40 ` [PATCHv3 09/12] atomics: switch to generated atomic-long Mark Rutland
2018-07-05 16:40 ` [PATCHv3 10/12] atomics: switch to generated instrumentation Mark Rutland
2018-07-05 16:40 ` [PATCHv3 11/12] atomics: check generated headers are up-to-date Mark Rutland
2018-07-05 16:40 ` [PATCHv3 12/12] arm64: use instrumented atomics Mark Rutland
2018-07-06 13:16 ` [PATCHv3 00/12] atomics: generate atomic headers / instrument arm64 Will Deacon
2018-07-06 13:21 ` Peter Zijlstra
2018-07-13 15:06 ` Mark Rutland
2018-07-14 13:01 ` Ingo Molnar [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=20180714130130.GA23906@gmail.com \
--to=mingo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).