public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC v3] drm/i915: Eliminate devid sprinkle
Date: Mon, 26 Feb 2018 18:08:25 +0200	[thread overview]
Message-ID: <87po4r20p2.fsf@intel.com> (raw)
In-Reply-To: <151966038251.2350.15547633202608059107@mail.alporthouse.com>

On Mon, 26 Feb 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2018-02-26 14:00:37)
>> On Thu, 22 Feb 2018, Tvrtko Ursulin <tursulin@ursulin.net> wrote:
>> > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> >
>> > Introduce subplatform mask to eliminate throughout the code devid checking
>> > sprinkle, mostly courtesy of IS_*_UL[TX] macros.
>> >
>> > Subplatform mask initialization is moved either to static tables (Ironlake
>> > M) or runtime device info init (Pineview, Haswell, Broadwell, Skylake,
>> > Kabylake, Coffeelake and Cannonlake).
>> 
>> I thought Chris had the goal of separating runtime and static init, and
>> I very much agreed with that idea. Throw away the mkwrite stuff. This
>> patch seems to be at odds with that goal by tying a runtime init into
>> the same mask with statically initialized platform mask.
>
> Yes.
>
> In the extreme version of single platform LTO, we would bake one
> device-info stanza for every subplatform. That may be a little overkill
> (or rather too complicated for the user to know and too fine-grained to
> be useful). So the middle ground is that we have subplatform in the
> runtime_info, and the compiler has to do two loads. We can still benefit
> from using BIT() though.

Well, let's not conflate platform and subplatform into the same mask in
the same info for the short-term benefit, then?

And with that, I think we could go towards:

#define IS_BWD_ULT(dev_priv) (IS_BROADWELL(dev_priv) && IS_ULT(dev_priv))

where the IS_ULT would just check the subplatform mask.

I am not convinced it's worth overloading the subplatform bits.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-26 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  8:09 [RFC] drm/i915: Eliminate devid sprinkle Tvrtko Ursulin
2018-02-22  8:16 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-02-22  8:24 ` [RFC] " Chris Wilson
2018-02-22 10:39   ` Tvrtko Ursulin
2018-02-22  8:30 ` ✗ Fi.CI.BAT: warning for " Patchwork
2018-02-22  8:35   ` Chris Wilson
2018-02-22  8:59     ` Tvrtko Ursulin
2018-02-22  9:05 ` [RFC v2] " Tvrtko Ursulin
2018-02-22 10:15   ` [RFC v3] " Tvrtko Ursulin
2018-02-22 10:27     ` Chris Wilson
2018-02-22 10:59     ` Chris Wilson
2018-02-26 14:00     ` Jani Nikula
2018-02-26 15:53       ` Chris Wilson
2018-02-26 16:08         ` Jani Nikula [this message]
2018-02-22  9:25 ` ✗ Fi.CI.BAT: warning for drm/i915: Eliminate devid sprinkle (rev2) Patchwork
2018-02-22 10:47 ` ✗ Fi.CI.BAT: warning for drm/i915: Eliminate devid sprinkle (rev3) 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=87po4r20p2.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=tursulin@ursulin.net \
    /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