Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 0/3] lib/i915/perf: Speed up the build
Date: Tue, 4 Apr 2023 10:59:50 +0300	[thread overview]
Message-ID: <25b355d0-cd89-f325-ef80-eb063caee083@intel.com> (raw)
In-Reply-To: <20230403174800.19621-1-ville.syrjala@linux.intel.com>

On 03/04/2023 20:47, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The perf xml stuff generates terrible C code that is giving
> gcc a big headache and leading to disgustingly long build
> times. Try to generate a bit more sensible code to speed
> up the build.
>
> Total build time change for the series:
> $ ninja -Cbuild  clean
> $ time ninja -Cbuild
>   ADL (4+8 cores):
>    - real        1m18,244s
>    + real        0m36,695s
>   VLV (2 cores):
>    - real        17m29.100s
>    + real        9m44.268s
>
> For comparison this is what I get if I skip all the perf xml
> files apart from hsw:
>   ADL:
>    real  0m20,080s
>   VLV
>    real  7m3.045s
>
> Thinking of further ways to reduce this... There are about a
> thousand "Ext" metric sets. Are those *actually* useful or
> could we just skip them? That would give us a total build
> time of:
>   ADL:
>    real  0m24,593s
>   VLV:
>    real  8m15.977s
>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>


Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>


>
> Ville Syrjälä (3):
>    lib/i915/perf: Stop generating silly C code
>    lib/i915/perf: Stop making copies of the registers
>    lib/i915/perf: Convert the metric counters to an array as well
>
>   .../perf-configs/perf-metricset-codegen.py    | 81 ++++++++++++++-----
>   .../perf-configs/perf-registers-codegen.py    | 30 +++----
>   lib/i915/perf.h                               |  8 +-
>   3 files changed, 78 insertions(+), 41 deletions(-)
>

      parent reply	other threads:[~2023-04-04  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 17:47 [igt-dev] [PATCH i-g-t 0/3] lib/i915/perf: Speed up the build Ville Syrjala
2023-04-03 17:47 ` [igt-dev] [PATCH i-g-t 1/3] lib/i915/perf: Stop generating silly C code Ville Syrjala
2023-04-03 17:47 ` [igt-dev] [PATCH i-g-t 2/3] lib/i915/perf: Stop making copies of the registers Ville Syrjala
2023-04-03 17:48 ` [igt-dev] [PATCH i-g-t 3/3] lib/i915/perf: Convert the metric counters to an array as well Ville Syrjala
2023-04-03 19:07 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/i915/perf: Speed up the build Patchwork
2023-04-04  1:27 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-04  7:59 ` Lionel Landwerlin [this message]

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=25b355d0-cd89-f325-ef80-eb063caee083@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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