From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v4 0/4] Handle dma fences in dirtyfb ioctl
Date: Fri, 1 Sep 2023 12:34:56 +0300 [thread overview]
Message-ID: <20230901093500.3463046-1-jouni.hogander@intel.com> (raw)
Currently i915 dirtyfb ioctl is not taking dma fences into
account. This works with features like FBC, PSR, DRRS because our gem
code is triggering flush again when rendering completes. We are
targeting in getting rid of frontbuffer tracking code: Flusing hook
from gem code will be removed as well.
This patch set is adding dma fence handling into i915 dirtyfb ioctl.
v4:
- Move invalidate back being done before cb is added
v3:
- Check frontbuffer bits before adding any fence fb
- Invalidate only when adding fence cb succeeds
- Check schedule work success rather than work being pending
- Init flush work when frontbuffer struct is initialized
v2:
- Clear fbc and psr busy bits on flip
- Check if flush work is already pending
- Use dma_resv_get_singleton
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Jouni Högander (4):
drm/i915/fbc: Clear frontbuffer busy bits on flip
drm/i915/psr: Clear frontbuffer busy bits on flip
drm/i915: Add new frontbuffer tracking interface to queue flush
drm/i915: Handle dma fences in dirtyfb callback
drivers/gpu/drm/i915/display/intel_fb.c | 60 ++++++++++++++++++-
drivers/gpu/drm/i915/display/intel_fbc.c | 6 +-
.../gpu/drm/i915/display/intel_frontbuffer.c | 28 +++++++++
.../gpu/drm/i915/display/intel_frontbuffer.h | 4 ++
drivers/gpu/drm/i915/display/intel_psr.c | 6 ++
5 files changed, 97 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-01 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:34 Jouni Högander [this message]
2023-09-01 9:34 ` [Intel-gfx] [PATCH v4 1/4] drm/i915/fbc: Clear frontbuffer busy bits on flip Jouni Högander
2023-09-04 7:25 ` Coelho, Luciano
2023-09-04 8:40 ` Hogander, Jouni
2023-09-04 8:52 ` Coelho, Luciano
2023-09-01 9:34 ` [Intel-gfx] [PATCH v4 2/4] drm/i915/psr: " Jouni Högander
2023-09-01 9:34 ` [Intel-gfx] [PATCH v4 3/4] drm/i915: Add new frontbuffer tracking interface to queue flush Jouni Högander
2023-09-01 9:35 ` [Intel-gfx] [PATCH v4 4/4] drm/i915: Handle dma fences in dirtyfb callback Jouni Högander
2023-09-01 11:09 ` [Intel-gfx] [PATCH v4 0/4] Handle dma fences in dirtyfb ioctl Ville Syrjälä
2023-09-04 9:34 ` Hogander, Jouni
2023-09-01 14:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Handle dma fences in dirtyfb ioctl (rev6) Patchwork
2023-09-01 15:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-02 0:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-04 5:22 ` Hogander, Jouni
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=20230901093500.3463046-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@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