From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, "Ursulin,
Tvrtko" <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH 0/6] drm/i915: start splitting off runtime device info
Date: Wed, 2 Jan 2019 10:17:54 +0000 [thread overview]
Message-ID: <2d73f783-cdd7-89ed-a03c-99c9101b2703@linux.intel.com> (raw)
In-Reply-To: <87va37l8wx.fsf@intel.com>
On 02/01/2019 09:13, Jani Nikula wrote:
> On Tue, 01 Jan 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> Quoting Jani Nikula (2018-12-31 14:56:40)
>>> The mkwrite_device_info removal series [1] seems to have stalled. I'm
>>> trying to nudge things forward a bit with this series. This isn't near
>>> as complete as Tvrtko's work, but does some of the prep work I wanted,
>>> specifically using INTEL_INFO() and RUNTIME_INFO() to access the
>>> fields. There are obviously conflicts, but mostly I think this should
>>> make the rest of Tvrtko's work easier, not harder.
>>>
>>> BR,
>>> Jani.
>>>
>>>
>>> [1] https://patchwork.freedesktop.org/series/52381/
>>>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
>>>
>>>
>>> Jani Nikula (6):
>>> drm/i915: start moving runtime device info to a separate struct
>>> drm/i915/reg: abstract display_mmio_offset access
>>> drm/i915: pass dev_priv to intel_device_info_runtime_init()
>>> drm/i915: always use INTEL_INFO() to access device info
>>> drm/i915: drop intel_device_info_dump()
>>> drm/i915: rename dev_priv info to __info to avoid usage
>>
>> Looked ok, and didn't see anything odd compared to my own attempts.
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Thanks for the review.
>
> Tvrtko, I'd still like to get your ack before I go ahead and push
> these. Also, do you think you'll have time in the near future to pick up
> your series, or shall I?
I missed Chris had already reviewed it. Yeah, series looks fine to me.
With regards to the second part, after your work what I think would be
left from mine is:
* move some more fields/flags to runtime info
* subplatform/devid consolidation
* looking at how to wean selftests off modifying the gen field
* maybe introducting INTEL_SSEU to avoid many RUNTIME_INFO(...)->sseu
If you are in a hurry and have time you can take over, or if you are
just in a hurry I might be able to do within a week or two.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-02 10:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 14:56 [PATCH 0/6] drm/i915: start splitting off runtime device info Jani Nikula
2018-12-31 14:56 ` [PATCH 1/6] drm/i915: start moving runtime device info to a separate struct Jani Nikula
2019-01-02 9:27 ` Tvrtko Ursulin
2019-01-02 10:21 ` Jani Nikula
2018-12-31 14:56 ` [PATCH 2/6] drm/i915/reg: abstract display_mmio_offset access Jani Nikula
2019-01-02 9:37 ` Tvrtko Ursulin
2018-12-31 14:56 ` [PATCH 3/6] drm/i915: pass dev_priv to intel_device_info_runtime_init() Jani Nikula
2019-01-02 9:38 ` Tvrtko Ursulin
2018-12-31 14:56 ` [PATCH 4/6] drm/i915: always use INTEL_INFO() to access device info Jani Nikula
2019-01-02 9:58 ` Tvrtko Ursulin
2018-12-31 14:56 ` [PATCH 5/6] drm/i915: drop intel_device_info_dump() Jani Nikula
2019-01-02 10:02 ` Tvrtko Ursulin
2019-01-02 10:42 ` Jani Nikula
2019-01-02 11:09 ` Tvrtko Ursulin
2018-12-31 14:56 ` [PATCH 6/6] drm/i915: rename dev_priv info to __info to avoid usage Jani Nikula
2019-01-02 10:04 ` Tvrtko Ursulin
2019-01-02 10:44 ` Jani Nikula
2019-01-02 11:10 ` Tvrtko Ursulin
2018-12-31 15:07 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: start splitting off runtime device info Patchwork
2018-12-31 15:10 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-31 15:43 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-31 17:53 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-01 10:31 ` [PATCH 0/6] " Chris Wilson
2019-01-02 9:13 ` Jani Nikula
2019-01-02 10:17 ` Tvrtko Ursulin [this message]
2019-01-02 11:19 ` Jani Nikula
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=2d73f783-cdd7-89ed-a03c-99c9101b2703@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=tvrtko.ursulin@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