public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 0/4] Device id consolidation
Date: Fri, 29 Mar 2019 09:17:03 +0000	[thread overview]
Message-ID: <2a3e85f2-82ba-d65b-b4f4-4774ed0098eb@linux.intel.com> (raw)
In-Reply-To: <155376599615.24691.4556086033538642703@skylake-alporthouse-com>


On 28/03/2019 09:39, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-03-28 09:23:24)
>>
>> On 26/03/2019 07:40, Tvrtko Ursulin wrote:
>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>
>>> Series removes device id checks from i915_drv.h macros and consolidates them to
>>> i915_pciids.h as the main "database", while making intel_device_info.c reference
>>> the former, expanding the existing concept of a platform mask by a few low bits
>>> reserved for sub-platform mask.
>>>
>>> This has a two-fold positive effect of firstly consolidating the list of device
>>> ids to one location, and secondly removing the if-ladders from every
>>> IS_<platfrom>_<subplatform> call site.
>>>
>>> Maintenance burden is not completely removed but should be improved. One case in
>>> point is that I have found some disagreements between device id listed in
>>> i915_pciids.h and i915_drv.h.
>>>
>>> At the same time platform mask code is generalized to an array of u32 to
>>> accomodate the addition of EHL and avoid spilling into u64 which would cause a
>>> small code size increase. Downside is that any platforms on the u32 boundary,
>>> like currently ICL and EHL, lose the benefit of optimizing the "IS_ICELAKE ||
>>> IS_ELKHARTLAKE" checks into a single conditional, although at the moment there
>>> aren't any such call-sites.
>>>
>>> Before vs after for the whole series:
>>>
>>>      text    data     bss     dec     hex filename
>>> 1891093   43903    7424 1942420  1da394 i915.ko.0
>>> 1890434   43903    7424 1941761  1da101 i915.ko.1
>>>
>>> add/remove: 12/3 grow/shrink: 92/121 up/down: 1974/-1769 (205)
>>> ...
>>> Total: Before=1286293, After=1286498, chg +0.02%
>>
>> After patch 4 v8:
>>
>>      text    data     bss     dec     hex filename
>> 1904423   43891    7424 1955738  1dd79a i915.ko.0
>> 1903354   43891    7424 1954669  1dd36d i915.ko.1
>>
>> add/remove: 8/3 grow/shrink: 94/124 up/down: 1623/-1889 (-266)
>> ...
>> Total: Before=1293823, After=1293557, chg -0.02%
> 
> The series is an improvement, both for the reader and for the compiler,
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Thanks.

Jani, Lucas? Passable? Still some objections?

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-03-29  9:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  7:40 [PATCH 0/4] Device id consolidation Tvrtko Ursulin
2019-03-26  7:40 ` [PATCH 1/4] drm/i915: Split Pineview device info into desktop and mobile Tvrtko Ursulin
2019-03-26  7:40 ` [PATCH 2/4] drm/i915: Remove redundant device id from IS_IRONLAKE_M macro Tvrtko Ursulin
2019-03-26  7:40 ` [PATCH 3/4] drm/i915: Split some PCI ids into separate groups Tvrtko Ursulin
2019-03-26  7:40 ` [PATCH 4/4] drm/i915: Introduce concept of a sub-platform Tvrtko Ursulin
2019-03-26  8:39   ` Jani Nikula
2019-03-26  9:34     ` Jani Nikula
2019-03-26  9:53       ` Chris Wilson
2019-03-27 11:35         ` Tvrtko Ursulin
2019-03-27 11:41           ` Chris Wilson
2019-03-27 12:03             ` Jani Nikula
2019-03-27 14:33               ` Tvrtko Ursulin
2019-03-27 15:06                 ` Jani Nikula
2019-03-27 11:37     ` Tvrtko Ursulin
2019-03-27 14:23   ` [PATCH v8 " Tvrtko Ursulin
2019-03-29  9:54     ` Jani Nikula
2019-03-29 12:10       ` Tvrtko Ursulin
2019-03-29 13:10         ` Jani Nikula
2019-03-26 15:59 ` ✗ Fi.CI.CHECKPATCH: warning for Device id consolidation Patchwork
2019-03-26 16:01 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-26 16:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-26 23:06 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-27 17:52 ` ✗ Fi.CI.CHECKPATCH: warning for Device id consolidation (rev2) Patchwork
2019-03-27 17:54 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-27 18:38 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-01 16:18   ` Tvrtko Ursulin
2019-03-28  9:23 ` [PATCH 0/4] Device id consolidation Tvrtko Ursulin
2019-03-28  9:39   ` Chris Wilson
2019-03-29  9:17     ` Tvrtko Ursulin [this message]
2019-03-28 12:43 ` ✓ Fi.CI.IGT: success for Device id consolidation (rev2) Patchwork

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=2a3e85f2-82ba-d65b-b4f4-4774ed0098eb@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=jani.nikula@intel.com \
    --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