From: Kees Cook <keescook@chromium.org>
To: jarmo.tiitto@gmail.com
Cc: Bill Wendling <morbo@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH] pgo: rename the raw profile file to vmlinux.profraw
Date: Tue, 1 Jun 2021 15:55:31 -0700 [thread overview]
Message-ID: <202106011555.A7E9BE38@keescook> (raw)
In-Reply-To: <5615959.Mqr2uNrfH2@hyperiorarchmachine>
On Wed, Jun 02, 2021 at 12:40:25AM +0300, jarmo.tiitto@gmail.com wrote:
> Yes, my future intention is that there will be one *.profraw file per module.
> And curiously I would also have renamed the current profile data file to
> "vmlinux.profraw" to disambiguate it from what part of kernel generated it.
>
> I already wrote an small fix up that I think should be part of the upstream
> code so that profiling the vmlinux works better.
> It filters out any module originated content from vmlinux.profraw.
>
> Above will be probably a good exercise for me.
>
> Next, my future v2 module profiling machinery
> would probably follow on top of your work.
Okay, great; thanks for digging into it! :)
--
Kees Cook
next prev parent reply other threads:[~2021-06-01 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 20:20 [PATCH] pgo: rename the raw profile file to vmlinux.profraw Bill Wendling
2021-05-31 20:29 ` Nathan Chancellor
2021-06-01 8:24 ` Bill Wendling
2021-06-01 19:13 ` Kees Cook
2021-06-01 21:40 ` jarmo.tiitto
2021-06-01 22:55 ` Kees Cook [this message]
2021-06-01 19:17 ` Kees Cook
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=202106011555.A7E9BE38@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-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@google.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 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.