Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 1 Jun 2021 15:55:31 -0700
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
Message-ID: <202106011555.A7E9BE38@keescook>
References: <20210531202044.426578-1-morbo@google.com>
 <CAGG=3QVdXxLf0T9+n9FidrRcfdWY36m-i=4kPRJjOojWhjiywg@mail.gmail.com>
 <202106011210.B5A8881214@keescook>
 <5615959.Mqr2uNrfH2@hyperiorarchmachine>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5615959.Mqr2uNrfH2@hyperiorarchmachine>
Precedence: bulk

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