From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: uma.shankar@intel.com, chaitanya.kumar.borah@intel.com,
maarten.lankhorst@linux.intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 0/6] Cursor Fault Fixes
Date: Mon, 05 Feb 2024 15:22:23 +0200 [thread overview]
Message-ID: <875xz3dp0w.fsf@intel.com> (raw)
In-Reply-To: <20240205064836.3645402-1-chaitanya.kumar.borah@intel.com>
On Mon, 05 Feb 2024, Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com> wrote:
> This series is based on top of [1] floated by Maarten.
> To fix regressions seen in CI, following changes were made on top of the
> original series.
You've sent at least three versions of this in the past 24 hours, with
no indication of the version. Please use the -vN parameter in git
format-patch or git send-email to indicate the series version number in
patch subjects, so it's easier for people to track.
Thanks,
Jani.
>
> 1. add a check in the plane state destroy hook to not move forward if the vblank worker is scheduled.
> 2. add checks before accessing frame buffer object (we are not sure yet how much this helps but we have found that this operation causes dump stacks)
> 3. do not defer the intel atomic cleanup into a work queue, instead execute it at the end of atomic commit tail.
>
> While this series is in noway a complete or proper solution it is meant to trigger a discussion to arrive at one.
>
> [1] https://patchwork.freedesktop.org/series/126934/
>
> v2: Add missing patch
> v3: Remove misleading error log
> Change condition to access fb object
>
> Chaitanya Kumar Borah (3):
> drm/i915: do not destroy plane state if cursor unpin worker is
> scheduled
> drm/i915: Add sanity check before accessing fb buffer object
> drm/i915: do not defer cleanup work
>
> Maarten Lankhorst (2):
> drm: Add drm_vblank_work_flush_all().
> drm/i915: Use the same vblank worker for atomic unpin
>
> Ville Syrjälä (1):
> drm/i915: Use vblank worker to unpin old legacy cursor fb safely
>
> drivers/gpu/drm/drm_vblank_work.c | 22 ++++++++
> .../gpu/drm/i915/display/intel_atomic_plane.c | 53 ++++++++++++++++++-
> .../gpu/drm/i915/display/intel_atomic_plane.h | 4 ++
> drivers/gpu/drm/i915/display/intel_crtc.c | 27 ++++++++++
> drivers/gpu/drm/i915/display/intel_cursor.c | 26 ++++++++-
> drivers/gpu/drm/i915/display/intel_cursor.h | 3 ++
> drivers/gpu/drm/i915/display/intel_display.c | 11 ++--
> .../drm/i915/display/intel_display_types.h | 3 ++
> include/drm/drm_vblank_work.h | 2 +
> 9 files changed, 142 insertions(+), 9 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-05 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 6:48 [PATCH 0/6] Cursor Fault Fixes Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH 1/6] drm: Add drm_vblank_work_flush_all() Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH 2/6] drm/i915: Use vblank worker to unpin old legacy cursor fb safely Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH 3/6] drm/i915: Use the same vblank worker for atomic unpin Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH 4/6] drm/i915: do not destroy plane state if cursor unpin worker is scheduled Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH v2 5/6] drm/i915: Add sanity check before accessing fb buffer object Chaitanya Kumar Borah
2024-02-05 6:48 ` [PATCH 6/6] drm/i915: do not defer cleanup work Chaitanya Kumar Borah
2024-02-05 9:21 ` ✗ Fi.CI.BUILD: failure for Cursor Fault Fixes (rev3) Patchwork
2024-02-05 13:22 ` Jani Nikula [this message]
2024-02-05 17:14 ` [PATCH 0/6] Cursor Fault Fixes Borah, Chaitanya Kumar
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 10:10 Chaitanya Kumar Borah
2024-02-05 4:31 Chaitanya Kumar Borah
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=875xz3dp0w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.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 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.