lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 Jan 2021 17:34:29 -0800
From:   Nick Desaulniers <>
To:     Sedat Dilek <>
Cc:     Bill Wendling <>, Jonathan Corbet <>,
        Masahiro Yamada <>,
        Linux Doc Mailing List <>,
        LKML <>,
        Linux Kbuild mailing list <>,
        Clang-Built-Linux ML <>,
        Andrew Morton <>,
        Nathan Chancellor <>,
        Sami Tolvanen <>
Subject: Re: [PATCH] pgo: add clang's Profile Guided Optimization infrastructure

On Wed, Jan 20, 2021 at 6:21 PM Sedat Dilek <> wrote:
> Hi,
> When I looked through the code I wondered why we do not add a
> "CONFIG_PGO_CLANG_PROFDATA" which can be helpful when doing the PGO
> rebuild with a vmlinux.profdata.
> This introduces a "PGO_PROFDATA" to turn on/off to pass
> "-fprofile-use=vmlinux.profdata" (see CFLAGS_PGO_CLANG_PROFDATA in
> top-level Makefile).
> If we turn off via "PGO_PROFILE := n" in several Makefiles - we should
> do the same and add "PGO_PROFDATA := n" to the same Makefiles?
> Please see the attached diff.

This is a good idea; something that I brought up in initial code
review (on github).  Would it be ok with you to land the core first,
then follow up with this suggestion?

Also, AutoFDO production builds are so incredibly similar to PGO
builds that I could see a possible path forward:
1. land PGO upstream
2. adds docs for AutoFDO
3. consider a config for hardcoding the location of the profiling data
so that we don't need to specify it at the command line invocation of
~Nick Desaulniers

Powered by blists - more mailing lists