Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/2] Handle dma fences in dirtyfb ioctl
Date: Tue, 18 Apr 2023 08:22:19 +0300	[thread overview]
Message-ID: <20230418052221.593983-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.

Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Jouni Högander (2):
  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       | 54 +++++++++++++++++--
 .../gpu/drm/i915/display/intel_frontbuffer.c  | 33 ++++++++++++
 .../gpu/drm/i915/display/intel_frontbuffer.h  |  4 ++
 3 files changed, 88 insertions(+), 3 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-04-18  5:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  5:22 Jouni Högander [this message]
2023-04-18  5:22 ` [Intel-gfx] [PATCH 1/2] drm/i915: Add new frontbuffer tracking interface to queue flush Jouni Högander
2023-04-18  5:22 ` [Intel-gfx] [PATCH 2/2] drm/i915: Handle dma fences in dirtyfb callback Jouni Högander
2023-04-18  5:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Handle dma fences in dirtyfb ioctl Patchwork
2023-04-18  6:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-18 11:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=20230418052221.593983-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