public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Collect both user and kernel events for autofdo tests and autoprofiledbootstrap
Date: Fri, 30 Jun 2023 10:51:47 +0200	[thread overview]
Message-ID: <CAFiYyc3V1QXShpObSqMaBn3h+YyR9icGS0Ks0s+pUsSSKs6ZOQ@mail.gmail.com> (raw)
In-Reply-To: <MN0PR21MB34844532CF2CD395DE99B07E912AA@MN0PR21MB3484.namprd21.prod.outlook.com>

On Fri, Jun 30, 2023 at 7:28 AM Eugene Rozenfeld via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> When we collect just user events for autofdo with lbr we get some events where branch
> sources are kernel addresses and branch targets are user addresses. Without kernel MMAP
> events create_gcov can't make sense of kernel addresses. Currently create_gcov fails if
> it can't map at least 95% of events. We sometimes get below this threshold with just
> user events. The change is to collect both user events and kernel events.

Does this require elevated privileges?  Can we instead "fix" create_gcov here?

> Tested on x86_64-pc-linux-gnu.
>
> ChangeLog:
>
>         * Makefile.in: Collect both kernel and user events for autofdo
>         * Makefile.tpl: Collect both kernel and user events for autofdo
>
> gcc/testsuite/ChangeLog:
>
>         * lib/target-supports.exp: Collect both kernel and user events for autofdo
> ---
>  Makefile.in                           | 2 +-
>  Makefile.tpl                          | 2 +-
>  gcc/testsuite/lib/target-supports.exp | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Makefile.in b/Makefile.in
> index f19a9db621e..04307ca561b 100644
> --- a/Makefile.in
> +++ b/Makefile.in
> @@ -404,7 +404,7 @@ MAKEINFO = @MAKEINFO@
>  EXPECT = @EXPECT@
>  RUNTEST = @RUNTEST@
>
> -AUTO_PROFILE = gcc-auto-profile -c 10000000
> +AUTO_PROFILE = gcc-auto-profile --all -c 10000000
>
>  # This just becomes part of the MAKEINFO definition passed down to
>  # sub-makes.  It lets flags be given on the command line while still
> diff --git a/Makefile.tpl b/Makefile.tpl
> index 3a5b7ed3c92..d0fe7e2fb77 100644
> --- a/Makefile.tpl
> +++ b/Makefile.tpl
> @@ -407,7 +407,7 @@ MAKEINFO = @MAKEINFO@
>  EXPECT = @EXPECT@
>  RUNTEST = @RUNTEST@
>
> -AUTO_PROFILE = gcc-auto-profile -c 10000000
> +AUTO_PROFILE = gcc-auto-profile --all -c 10000000
>
>  # This just becomes part of the MAKEINFO definition passed down to
>  # sub-makes.  It lets flags be given on the command line while still
> diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
> index 4d04df2a709..b16853d76df 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -704,7 +704,7 @@ proc check_effective_target_keeps_null_pointer_checks { } {
>  # this allows parallelism of 16 and higher of parallel gcc-auto-profile
>  proc profopt-perf-wrapper { } {
>      global srcdir
> -    return "$srcdir/../config/i386/gcc-auto-profile -m8 "
> +    return "$srcdir/../config/i386/gcc-auto-profile --all -m8 "
>  }
>
>  # Return true if profiling is supported on the target.
> --
> 2.25.1
>

  reply	other threads:[~2023-06-30  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  5:27 Eugene Rozenfeld
2023-06-30  8:51 ` Richard Biener [this message]
2023-06-30  8:59   ` Sam James
2023-06-30 21:44     ` [EXTERNAL] " Eugene Rozenfeld
2023-06-30 22:05       ` Eugene Rozenfeld
2023-07-03  7:46         ` Richard Biener
2023-07-05 21:15           ` Eugene Rozenfeld
2023-07-06  6:23             ` Richard Biener

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=CAFiYyc3V1QXShpObSqMaBn3h+YyR9icGS0Ks0s+pUsSSKs6ZOQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=Eugene.Rozenfeld@microsoft.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).