From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Michael Cheng <michael.cheng@intel.com>
Subject: Re: [Intel-gfx] [RFC 0/2] Compile out integrated
Date: Wed, 2 Feb 2022 11:51:35 +0000 [thread overview]
Message-ID: <39e3d23e-3f15-2abf-df61-8ad2eda47d88@linux.intel.com> (raw)
In-Reply-To: <20220201111533.250242-1-tvrtko.ursulin@linux.intel.com>
On 01/02/2022 11:15, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Quicky and dirty hack based on some old ideas. Thought maybe the approach might
> interest the Arm port guys. But with IS_GEN_RANGE removed easy gains are not so
> big so meh.. Maybe some more easy wins with IS_DISPLAY_VER but I haven't looked
> into that side.
>
> 3884664 449681 6720 4341065 423d49 i915.ko.tip
> 3599989 429034 6688 4035711 3d947f i915.ko.noigp
>
> Note debug kconfig so everything is inflated. Whether or not the relative gain
> would change with production kconfig I am not sure.
Non debug build for the record:
text data bss dec hex filename
2188446 20528 2944 2211918 21c04e i915.ko.tip
1926865 17776 2944 1947585 1db7c1 i915.ko.noigpu
So around ~12% of the driver eliminated as dead code with the easy and
incomplete approach. Not bad considering no clean split on Gen12, gen
based if-ladder are mostly untouched and no LTO.
Regards,
Tvrtko
prev parent reply other threads:[~2022-02-02 11:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 11:15 [Intel-gfx] [RFC 0/2] Compile out integrated Tvrtko Ursulin
2022-02-01 11:15 ` [Intel-gfx] [RFC 1/2] igp kconfig Tvrtko Ursulin
2022-02-01 11:15 ` [Intel-gfx] [RFC 2/2] jsl/ehl Tvrtko Ursulin
2022-02-01 11:26 ` Jani Nikula
2022-02-01 13:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Compile out integrated Patchwork
2022-02-01 13:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-01 13:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-01 16:55 ` [Intel-gfx] [RFC 0/2] " Lucas De Marchi
2022-02-01 17:09 ` Jani Nikula
2022-02-01 17:28 ` Lucas De Marchi
2022-02-02 10:26 ` Tvrtko Ursulin
2022-02-02 11:20 ` Jani Nikula
2022-02-02 12:17 ` Tvrtko Ursulin
2022-02-02 12:41 ` Jani Nikula
2022-02-02 16:26 ` Lucas De Marchi
2022-02-08 10:31 ` Tvrtko Ursulin
2022-02-08 20:34 ` Lucas De Marchi
2022-02-01 17:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-02-02 11:51 ` Tvrtko Ursulin [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=39e3d23e-3f15-2abf-df61-8ad2eda47d88@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=michael.cheng@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