From: Sedat Dilek <sedat.dilek@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Matthias Kaehlcke <mka@chromium.org>,
Dmitry Vyukov <dvyukov@google.com>,
Greg Hackmann <ghackmann@google.com>,
Luis Lozano <llozano@google.com>,
Michael Davidson <md@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Paul Lawrence <paullawrence@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Ingo Molnar <mingo@kernel.org>,
linux-mm@kvack.org, llvmlinux@lists.linuxfoundation.org,
sil2review@lists.osadl.org, Jan Beulich <JBeulich@suse.com>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
Colin King <colin.king@canonical.com>
Subject: Re: [llvmlinux] clang fails on linux-next since commit 8bf705d13039
Date: Mon, 30 Jul 2018 14:28:42 +0200 [thread overview]
Message-ID: <CA+icZUVEYs0Y+vdwB9o8bQf3QiOGJ_vZKnD3LGXVeAsok95S6w@mail.gmail.com> (raw)
In-Reply-To: <20180730094622.av7wlyrkl3rn37mp@lakrids.cambridge.arm.com>
On Mon, Jul 30, 2018 at 11:46 AM, Mark Rutland <mark.rutland@arm.com> wrote:
> On Mon, Jul 30, 2018 at 11:40:49AM +0200, Sedat Dilek wrote:
>> What are your plans to have...
>>
>> 4d2b25f630c7 locking/atomics: Instrument cmpxchg_double*()
>> f9881cc43b11 locking/atomics: Instrument xchg()
>> df79ed2c0643 locking/atomics: Simplify cmpxchg() instrumentation
>> 00d5551cc4ee locking/atomics/x86: Reduce arch_cmpxchg64*() instrumentation
>>
>> ...for example in Linux 4.18 or 4.17.y?
>
> I have no plans to have these backported.
>
I guess this is 4.19 material?
Not sure, if I will try a "backport" myself or wait for the fix in clang.
Thanks Mark.
Regards,
- Sedat -
next prev parent reply other threads:[~2018-07-30 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 9:09 Sedat Dilek
2018-07-30 9:19 ` Mark Rutland
2018-07-30 9:40 ` Sedat Dilek
2018-07-30 9:46 ` Mark Rutland
2018-07-30 12:28 ` Sedat Dilek [this message]
2018-07-30 12:57 ` Mark Rutland
2018-07-30 16:35 ` Nick Desaulniers
2018-07-30 16:40 ` Sedat Dilek
2018-07-31 7:04 ` Sedat Dilek
2018-07-31 7:35 ` Sedat Dilek
2018-07-31 11:07 ` Sedat Dilek
2018-07-31 7:24 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2018-03-17 11:13 Lukas Bulwahn
2018-03-19 6:43 ` Dmitry Vyukov
2018-03-19 17:29 ` Matthias Kaehlcke
[not found] ` <99fbbbe3-df05-446b-9ce0-55787ea038f3@googlegroups.com>
2018-05-06 10:44 ` Dmitry Vyukov
2018-05-06 10:48 ` Sedat Dilek
2018-05-07 7:34 ` Dmitry Vyukov
2018-05-28 16:05 ` [llvmlinux] " Sedat Dilek
2018-05-29 6:49 ` Jan Beulich
2018-06-01 13:14 ` Sedat Dilek
2018-07-29 18:12 ` Sedat Dilek
2018-07-30 8:21 ` Mark Rutland
2018-07-30 9:29 ` Sedat Dilek
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=CA+icZUVEYs0Y+vdwB9o8bQf3QiOGJ_vZKnD3LGXVeAsok95S6w@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=JBeulich@suse.com \
--cc=colin.king@canonical.com \
--cc=dvyukov@google.com \
--cc=ghackmann@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=llozano@google.com \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=mark.rutland@arm.com \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=ndesaulniers@google.com \
--cc=paullawrence@google.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=sil2review@lists.osadl.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