From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] drm/i915: move dpll_info inside intel_shared_dpll
Date: Tue, 20 Mar 2018 11:57:00 +0200 [thread overview]
Message-ID: <20180320095700.GR5453@intel.com> (raw)
In-Reply-To: <20180320062423.9166-1-lucas.demarchi@intel.com>
On Mon, Mar 19, 2018 at 11:24:16PM -0700, Lucas De Marchi wrote:
>
> This is an alternative to my previous patch
> "drm/i915: Remove hole and padding from intel_shared_dpll".
>
> Not sure if I split this too much, but I think it's easier to review
> this way. We can always squash them if wanted.
>
> As can be seen below this reduces .text and size of our structs, but
> maybe more important it puts the const data together.
>
> text data bss dec hex filename
> 1753856 69541 5316 1828713 1be769 drivers/gpu/drm/i915/i915.ko
> 1753668 69541 5316 1828525 1be6ad drivers/gpu/drm/i915/i915.ko.new
>
> Ville, instead of adding a pointer I decided to copy the struct, just
> because I thought we were going through too many indirections while for
> example accesssing pll->info->funcs->get_hw_state().
I don't particularly like the copy since it means no const.
>
> struct sizes:
> before after
> intel_shared_dpll 152 128
> i915_drm_private 32112 31968
>
> Lucas De Marchi (7):
> drm/i915: move dpll_info to header
> drm/i915: embed dpll_info inside intel_shared_dpll
> drm/i915: use funcs from dpll_info embedded in intel_shared_dpll
> drm/i915: use name from dpll_info embedded in intel_shared_dpll
> drm/i915: use id from dpll_info embedded in intel_shared_dpll
> drm/i915: use flags from dpll_info embedded in intel_shared_dpll
> drm/i915: rename dpll_info to intel_dpll_info
>
> drivers/gpu/drm/i915/i915_debugfs.c | 3 +-
> drivers/gpu/drm/i915/intel_ddi.c | 8 +-
> drivers/gpu/drm/i915/intel_display.c | 25 ++---
> drivers/gpu/drm/i915/intel_dpll_mgr.c | 198 +++++++++++++++++-----------------
> drivers/gpu/drm/i915/intel_dpll_mgr.h | 53 +++++----
> 5 files changed, 145 insertions(+), 142 deletions(-)
>
> --
> 2.14.3
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-03-20 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 6:24 [PATCH 0/7] drm/i915: move dpll_info inside intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 1/7] drm/i915: move dpll_info to header Lucas De Marchi
2018-03-20 9:56 ` Ville Syrjälä
2018-03-20 21:50 ` Lucas De Marchi
2018-03-21 10:25 ` Ville Syrjälä
2018-03-21 19:21 ` Lucas De Marchi
2018-03-20 6:24 ` [PATCH 2/7] drm/i915: embed dpll_info inside intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 3/7] drm/i915: use funcs from dpll_info embedded in intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 4/7] drm/i915: use name " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 5/7] drm/i915: use id " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 6/7] drm/i915: use flags " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 7/7] drm/i915: rename dpll_info to intel_dpll_info Lucas De Marchi
2018-03-20 6:40 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: move dpll_info inside intel_shared_dpll Patchwork
2018-03-20 6:57 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-03-20 9:57 ` Ville Syrjälä [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=20180320095700.GR5453@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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