From: Kees Cook <keescook@chromium.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Bill Wendling <morbo@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Jarmo Tiitto <jarmo.tiitto@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, clang-built-linux@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Fangrui Song <maskray@google.com>
Subject: Re: [PATCH v9] pgo: add clang's Profile Guided Optimization infrastructure
Date: Tue, 1 Jun 2021 11:53:43 -0700 [thread overview]
Message-ID: <202106011152.9E91FF6@keescook> (raw)
On Mon, May 31, 2021 at 02:12:46PM -0700, Nathan Chancellor wrote:
> On Wed, May 19, 2021 at 02:37:26PM -0700, Kees Cook wrote:
> > I've added this to patch to my -next tree now:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/clang/pgo&id=e1af496cbe9b4517428601a4e44fee3602dd3c15
> >
>
> Would this be appropriate to send? Someone sent some patches based on
> this work so it would be nice to solidify how they will get to Linus
> if/when the time comes :)
Yeah, good idea.
> https://lore.kernel.org/r/20210528200133.459022-1-jarmo.tiitto@gmail.com/
> https://lore.kernel.org/r/20210528200432.459120-1-jarmo.tiitto@gmail.com/
> https://lore.kernel.org/r/20210528200821.459214-1-jarmo.tiitto@gmail.com/
> https://lore.kernel.org/r/20210528201006.459292-1-jarmo.tiitto@gmail.com/
> https://lore.kernel.org/r/20210528201107.459362-1-jarmo.tiitto@gmail.com/
> https://lore.kernel.org/r/20210528201213.459483-1-jarmo.tiitto@gmail.com/
BTW, Jarmo, if you haven't had this suggested yet, I'd recommend using
this kind of a script for your email sending workflow to get a set of
threaded patches:
#!/bin/sh
set -x
MYSELF="Your Name <and.email@goes.here>"
prefix="PATCH"
# or
#prefix="PATCH v2"
# etc...
SHA="SHA your series is based on"
format_args="--cover-letter -n -o outgoing/"
maint_args="--norolestats"
mkdir -p outgoing
git format-patch $format_args --subject-prefix "$prefix" "$SHA"
./scripts/checkpatch.pl "$@" --codespell outgoing/0*patch
${EDITOR:-vi} outgoing/*
# Send patches
git send-email --transfer-encoding=8bit --8bit-encoding=UTF-8 \
--no-chain-reply-to --thread \
--from="$MYSELF" --cc="$MYSELF" \
--to-cmd="./scripts/get_maintainer.pl $maint_args -m" \
--cc-cmd="./scripts/get_maintainer.pl $maint_args --nom" \
outgoing/*
>
> Cheers,
> Nathan
>
> ======================================
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c45613c30803..0d03f6ccdb70 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14378,9 +14378,13 @@ F: include/uapi/linux/personality.h
> PGO BASED KERNEL PROFILING
> M: Sami Tolvanen <samitolvanen@google.com>
> M: Bill Wendling <wcw@google.com>
> +M: Kees Cook <keescook@chromium.org>
> R: Nathan Chancellor <nathan@kernel.org>
> R: Nick Desaulniers <ndesaulniers@google.com>
> +L: clang-built-linux@googlegroups.com
> S: Supported
> +B: https://github.com/ClangBuiltLinux/linux/issues
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/clang/pgo
I think I'm going to keep things combined in a single tree for now since the patch rate
is low:
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/clang/features
> F: Documentation/dev-tools/pgo.rst
> F: kernel/pgo/
>
I should likely do the same entry for CFI.
--
Kees Cook
next reply other threads:[~2021-06-01 18:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 18:53 Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 8:18 [PATCH] pgo: add clang's Profile Guided Optimization infrastructure Bill Wendling
2021-04-07 21:17 ` [PATCH v9] " Bill Wendling
2021-04-07 21:22 ` Kees Cook
2021-04-07 21:44 ` Fāng-ruì Sòng
2021-04-07 21:47 ` Nathan Chancellor
2021-04-07 21:58 ` Bill Wendling
2021-05-19 21:37 ` Kees Cook
2021-05-22 23:51 ` Bill Wendling
2021-05-31 21:12 ` Nathan Chancellor
2021-06-01 17:31 ` Nick Desaulniers
2021-06-12 16:59 ` Peter Zijlstra
2021-06-12 17:25 ` Bill Wendling
2021-06-12 18:15 ` Peter Zijlstra
2021-06-12 19:10 ` Bill Wendling
2021-06-12 19:28 ` Bill Wendling
2021-06-12 20:25 ` Peter Zijlstra
2021-06-12 20:56 ` Bill Wendling
2021-06-12 22:47 ` Bill Wendling
2021-06-13 18:07 ` Bill Wendling
2021-06-14 9:43 ` Peter Zijlstra
2021-06-14 10:18 ` Peter Zijlstra
2021-06-14 7:51 ` Peter Zijlstra
2021-06-14 9:01 ` Peter Zijlstra
2021-06-14 9:39 ` Bill Wendling
2021-06-14 10:44 ` Peter Zijlstra
2021-06-14 11:41 ` Bill Wendling
2021-06-14 11:43 ` Bill Wendling
2021-06-14 14:16 ` Marco Elver
2021-06-14 15:26 ` Kees Cook
2021-06-14 15:35 ` Peter Zijlstra
2021-06-14 16:22 ` Kees Cook
2021-06-14 18:07 ` Nick Desaulniers
2021-06-14 20:49 ` Nick Desaulniers
2021-06-14 15:46 ` Peter Zijlstra
2021-06-14 16:03 ` Nick Desaulniers
2021-06-12 20:20 ` Fangrui Song
2021-06-12 20:31 ` Peter Zijlstra
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=202106011152.9E91FF6@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=jarmo.tiitto@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=morbo@google.com \
--cc=natechancellor@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).