From: daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/7] drm/amd/display: Drop DRM private objects from amdgpu_dm
Date: Fri, 7 Aug 2020 10:29:12 +0200 [thread overview]
Message-ID: <20200807082912.GK6419@phenom.ffwll.local> (raw)
In-Reply-To: <20200730203642.17553-1-nicholas.kazlauskas@amd.com>
On Thu, Jul 30, 2020 at 04:36:35PM -0400, Nicholas Kazlauskas wrote:
> Based on the analysis of the bug from [1] the best course of action seems
> to be swapping off of DRM private objects back to subclassing DRM atomic
> state instead.
>
> This patch series implements this change, but not yet the other changes
> suggested in the threads from that bug - these will come later.
>
> CCing dri-devel per Daniel's suggestion since this issue brought
> some interesting misuse of private objects.
I ended up reading around a bit, and it feels like the sub-objects might
make a reasonable private state structure perhaps. Like dc_stream_state,
at least when reading around in e.g. dc_remove_stream_from_ctx.
But would need to come up with a plan how to integrate this on the other
os side of DC I guess :-)
Anyway I'd say more evidence that dc_state needs to subclass
drm_atomic_state.
Another thing I wondered is whether we should rename drm_atomic_state to
drm_atomic_state_update, so it's clear it's the container with the updated
states, not a real state object thing itself.
-Daniel
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=207383
>
> Nicholas Kazlauskas (7):
> drm/amd/display: Store tiling_flags and tmz_surface on dm_plane_state
> drm/amd/display: Reset plane when tiling flags change
> drm/amd/display: Avoid using unvalidated tiling_flags and tmz_surface
> in prepare_planes
> drm/amd/display: Use validated tiling_flags and tmz_surface in
> commit_tail
> drm/amd/display: Reset plane for anything that's not a FAST update
> drm/amd/display: Drop dm_determine_update_type_for_commit
> drm/amd/display: Replace DRM private objects with subclassed DRM
> atomic state
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 967 ++++++------------
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 13 +-
> 2 files changed, 343 insertions(+), 637 deletions(-)
>
> --
> 2.25.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-08-07 8:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 20:36 [PATCH 0/7] drm/amd/display: Drop DRM private objects from amdgpu_dm Nicholas Kazlauskas
2020-07-30 20:36 ` [PATCH 1/7] drm/amd/display: Store tiling_flags and tmz_surface on dm_plane_state Nicholas Kazlauskas
2020-08-05 21:04 ` Rodrigo Siqueira
2020-08-07 8:24 ` daniel
2020-07-30 20:36 ` [PATCH 2/7] drm/amd/display: Reset plane when tiling flags change Nicholas Kazlauskas
2020-07-30 20:50 ` Wu, Hersen
2020-08-05 21:11 ` Rodrigo Siqueira
2020-08-06 18:18 ` Kazlauskas, Nicholas
2020-07-30 20:36 ` [PATCH 3/7] drm/amd/display: Avoid using unvalidated tiling_flags and tmz_surface in prepare_planes Nicholas Kazlauskas
2020-08-05 21:12 ` Rodrigo Siqueira
2020-08-07 8:30 ` daniel
2020-08-07 14:29 ` Kazlauskas, Nicholas
2020-08-10 12:25 ` Daniel Vetter
2020-08-10 12:30 ` Christian König
2020-08-10 12:32 ` Daniel Vetter
2020-08-11 13:42 ` Marek Olšák
2020-08-12 13:54 ` Daniel Vetter
2020-08-17 6:23 ` Marek Olšák
2020-09-01 7:20 ` Daniel Vetter
2020-07-30 20:36 ` [PATCH 4/7] drm/amd/display: Use validated tiling_flags and tmz_surface in commit_tail Nicholas Kazlauskas
2020-08-05 21:15 ` Rodrigo Siqueira
2020-07-30 20:36 ` [PATCH 5/7] drm/amd/display: Reset plane for anything that's not a FAST update Nicholas Kazlauskas
2020-07-30 20:51 ` Wu, Hersen
2020-08-05 20:45 ` Rodrigo Siqueira
2020-08-06 18:27 ` Kazlauskas, Nicholas
2020-08-07 8:34 ` daniel
2020-08-07 14:26 ` Kazlauskas, Nicholas
2020-08-10 12:30 ` Daniel Vetter
2020-07-30 20:36 ` [PATCH 6/7] drm/amd/display: Drop dm_determine_update_type_for_commit Nicholas Kazlauskas
2020-08-05 20:48 ` Rodrigo Siqueira
2020-07-30 20:36 ` [PATCH 7/7] drm/amd/display: Replace DRM private objects with subclassed DRM atomic state Nicholas Kazlauskas
2020-08-05 20:37 ` Rodrigo Siqueira
2020-08-06 14:25 ` Kazlauskas, Nicholas
2020-08-07 8:40 ` daniel
2020-08-07 8:52 ` daniel
2020-08-07 14:32 ` Kazlauskas, Nicholas
2020-08-10 12:34 ` Daniel Vetter
2020-08-07 8:29 ` daniel [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=20200807082912.GK6419@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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