All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>,
	"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	mikita.lipski@amd.com, "Michel Dänzer" <michel@daenzer.net>
Subject: Re: [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks
Date: Fri, 1 Apr 2022 10:39:59 +0200	[thread overview]
Message-ID: <20220401083959.4trlcyuoffax3e7x@houat> (raw)
In-Reply-To: <20220331152021.2671937-1-daniel.vetter@ffwll.ch>

On Thu, Mar 31, 2022 at 05:20:21PM +0200, Daniel Vetter wrote:
> The stuff never really worked, and leads to lots of fun because it
> out-of-order frees atomic states. Which upsets KASAN, among other
> things.
> 
> For async updates we now have a more solid solution with the
> ->atomic_async_check and ->atomic_async_commit hooks. Support for that
> for msm and vc4 landed. nouveau and i915 have their own commit
> routines, doing something similar.
> 
> For everyone else it's probably better to remove the use-after-free
> bug, and encourage folks to use the async support instead. The
> affected drivers which register a legacy cursor plane and don't either
> use the new async stuff or their own commit routine are: amdgpu,
> atmel, mediatek, qxl, rockchip, sti, sun4i, tegra, virtio, and vmwgfx.
> 
> Inspired by an amdgpu bug report.
> 
> v2: Drop RFC, I think with amdgpu converted over to use
> atomic_async_check/commit done in
> 
> commit 674e78acae0dfb4beb56132e41cbae5b60f7d662
> Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Date:   Wed Dec 5 14:59:07 2018 -0500
> 
>     drm/amd/display: Add fast path for cursor plane updates
> 
> we don't have any driver anymore where we have userspace expecting
> solid legacy cursor support _and_ they are using the atomic helpers in
> their fully glory. So we can retire this.
> 
> v3: Paper over msm and i915 regression. The complete_all is the only
> thing missing afaict.
> 
> v4: Fixup i915 fixup ...
> 
> References: https://bugzilla.kernel.org/show_bug.cgi?id=199425
> References: https://lore.kernel.org/all/20220221134155.125447-9-maxime@cerno.tech/
> References: https://bugzilla.kernel.org/show_bug.cgi?id=199425
> Cc: Maxime Ripard <maxime@cerno.tech>
> Tested-by: Maxime Ripard <maxime@cerno.tech>
> Cc: mikita.lipski@amd.com
> Cc: Michel Dänzer <michel@daenzer.net>
> Cc: harry.wentland@amd.com
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
> Cc: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Acked-by: Maxime Ripard <maxime@cerno.tech>

Maxime

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>,
	"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	mikita.lipski@amd.com, harry.wentland@amd.com,
	"Michel Dänzer" <michel@daenzer.net>
Subject: Re: [Intel-gfx] [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks
Date: Fri, 1 Apr 2022 10:39:59 +0200	[thread overview]
Message-ID: <20220401083959.4trlcyuoffax3e7x@houat> (raw)
In-Reply-To: <20220331152021.2671937-1-daniel.vetter@ffwll.ch>

On Thu, Mar 31, 2022 at 05:20:21PM +0200, Daniel Vetter wrote:
> The stuff never really worked, and leads to lots of fun because it
> out-of-order frees atomic states. Which upsets KASAN, among other
> things.
> 
> For async updates we now have a more solid solution with the
> ->atomic_async_check and ->atomic_async_commit hooks. Support for that
> for msm and vc4 landed. nouveau and i915 have their own commit
> routines, doing something similar.
> 
> For everyone else it's probably better to remove the use-after-free
> bug, and encourage folks to use the async support instead. The
> affected drivers which register a legacy cursor plane and don't either
> use the new async stuff or their own commit routine are: amdgpu,
> atmel, mediatek, qxl, rockchip, sti, sun4i, tegra, virtio, and vmwgfx.
> 
> Inspired by an amdgpu bug report.
> 
> v2: Drop RFC, I think with amdgpu converted over to use
> atomic_async_check/commit done in
> 
> commit 674e78acae0dfb4beb56132e41cbae5b60f7d662
> Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Date:   Wed Dec 5 14:59:07 2018 -0500
> 
>     drm/amd/display: Add fast path for cursor plane updates
> 
> we don't have any driver anymore where we have userspace expecting
> solid legacy cursor support _and_ they are using the atomic helpers in
> their fully glory. So we can retire this.
> 
> v3: Paper over msm and i915 regression. The complete_all is the only
> thing missing afaict.
> 
> v4: Fixup i915 fixup ...
> 
> References: https://bugzilla.kernel.org/show_bug.cgi?id=199425
> References: https://lore.kernel.org/all/20220221134155.125447-9-maxime@cerno.tech/
> References: https://bugzilla.kernel.org/show_bug.cgi?id=199425
> Cc: Maxime Ripard <maxime@cerno.tech>
> Tested-by: Maxime Ripard <maxime@cerno.tech>
> Cc: mikita.lipski@amd.com
> Cc: Michel Dänzer <michel@daenzer.net>
> Cc: harry.wentland@amd.com
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
> Cc: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Acked-by: Maxime Ripard <maxime@cerno.tech>

Maxime

  parent reply	other threads:[~2022-04-01  8:40 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 15:20 [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Daniel Vetter
2022-03-31 15:20 ` [Intel-gfx] " Daniel Vetter
2022-03-31 19:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-31 20:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-01  8:39 ` Maxime Ripard [this message]
2022-04-01  8:39   ` [Intel-gfx] [PATCH] " Maxime Ripard
2022-04-06 21:57 ` Rob Clark
2022-04-06 21:57   ` [Intel-gfx] " Rob Clark
2022-04-07  1:27 ` Jessica Zhang
2022-04-07  1:27   ` [Intel-gfx] " Jessica Zhang
2022-04-07  9:33   ` Daniel Vetter
2022-04-07  9:33     ` [Intel-gfx] " Daniel Vetter
2022-04-07 22:51   ` Rob Clark
2022-04-07 22:51     ` [Intel-gfx] " Rob Clark
2022-04-07 22:59     ` Abhinav Kumar
2022-04-07 22:59       ` [Intel-gfx] " Abhinav Kumar
2022-04-07 23:12       ` Rob Clark
2022-04-07 23:12         ` [Intel-gfx] " Rob Clark
2022-04-09  4:04         ` Abhinav Kumar
2022-04-09  4:04           ` [Intel-gfx] " Abhinav Kumar
2022-04-12 23:36           ` Abhinav Kumar
2022-04-12 23:36             ` [Intel-gfx] " Abhinav Kumar
2022-04-13 11:20             ` Daniel Vetter
2022-04-13 11:20               ` [Intel-gfx] " Daniel Vetter
2022-04-28  8:08               ` Maxime Ripard
2022-04-28  8:08                 ` Maxime Ripard
2022-04-28 12:09                 ` Daniel Vetter
2022-04-28 12:09                   ` [Intel-gfx] " Daniel Vetter
2022-05-12  8:08                   ` Maxime Ripard
2022-05-12  8:08                     ` [Intel-gfx] " Maxime Ripard
2022-09-26 15:06               ` Melissa Wen
2022-09-26 15:06                 ` [Intel-gfx] " Melissa Wen
2022-04-07  7:49 ` Thomas Zimmermann
2022-04-07  7:49   ` Thomas Zimmermann
2022-04-07  9:30   ` Daniel Vetter
2022-04-07  9:30     ` [Intel-gfx] " Daniel Vetter
2022-04-07 12:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/atomic-helpers: remove legacy_cursor_update hacks (rev2) Patchwork
2022-04-07 13:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-07 18:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-02-16 11:12 [PATCH] drm/atomic-helpers: remove legacy_cursor_update hacks Daniel Vetter
2023-02-16 11:12 ` Daniel Vetter
2023-02-16 11:12 ` Daniel Vetter
2023-02-22 23:14 ` Rob Clark
2023-02-22 23:14   ` Rob Clark
2023-02-22 23:14   ` Rob Clark
2023-02-22 23:21   ` Rob Clark
2023-02-22 23:21     ` Rob Clark
2023-02-22 23:21     ` Rob Clark
2023-03-07 14:56 ` Maxime Ripard
2023-03-07 14:56   ` Maxime Ripard
2023-03-07 14:56   ` Maxime Ripard
2024-01-23  6:09   ` Jason-JH Lin (林睿祥)
2024-01-23  6:09     ` Jason-JH Lin (林睿祥)
2024-01-23  6:09     ` Jason-JH Lin (林睿祥)
2024-01-23  6:09     ` Jason-JH Lin (林睿祥)
2024-01-23  6:09     ` Jason-JH Lin (林睿祥)
2024-01-25 18:17     ` Daniel Vetter
2024-01-25 18:17       ` Daniel Vetter
2024-01-25 18:17       ` Daniel Vetter
2024-01-25 18:17       ` Daniel Vetter
2024-01-25 18:17       ` Daniel Vetter
2024-01-31  5:17       ` Jason-JH Lin (林睿祥)
2024-01-31  5:17         ` Jason-JH Lin (林睿祥)
2024-01-31  5:17         ` Jason-JH Lin (林睿祥)
2024-01-31  5:17         ` Jason-JH Lin (林睿祥)
2024-01-31  5:17         ` Jason-JH Lin (林睿祥)
2024-01-31  9:11         ` Daniel Vetter
2024-01-31  9:11           ` Daniel Vetter
2024-01-31  9:11           ` Daniel Vetter
2024-01-31  9:11           ` Daniel Vetter
2024-01-31  9:11           ` Daniel Vetter
2024-01-31 10:26           ` Dmitry Baryshkov
2024-01-31 10:26             ` Dmitry Baryshkov
2024-01-31 10:26             ` Dmitry Baryshkov
2024-01-31 11:28             ` Daniel Vetter
2024-01-31 11:28               ` Daniel Vetter
2024-01-31 11:28               ` Daniel Vetter
2024-01-31 11:28               ` Daniel Vetter
2024-01-31 11:28               ` Daniel Vetter
2020-10-21 16:32 [PATCH 1/3] " Daniel Vetter
2020-10-23 12:26 ` [PATCH] " Daniel Vetter

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=20220401083959.4trlcyuoffax3e7x@houat \
    --to=maxime@cerno.tech \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    --cc=mikita.lipski@amd.com \
    --cc=nicholas.kazlauskas@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.