From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: [Intel-xe] [PATCH v4 0/4] Frontbuffer tracking and dirtyfb
Date: Wed, 4 Oct 2023 18:21:55 +0200 [thread overview]
Message-ID: <9d2a6f00-14ad-41db-98bb-caaba43f70f5@linux.intel.com> (raw)
In-Reply-To: <20231002102359.3740026-1-jouni.hogander@intel.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Den 2023-10-02 kl. 12:23, skrev Jouni Högander:
> Generic dirtyfb implementation which Xe is currently using is doing
> atomic commit which is inefficient. We have now dma fence handling in
> our dirtyfb implementation. This works with Xe and CPU/GPU frontbuffer
> rendering as long as sync objects are imported by userspace
> (dma_buf_import_sync_file).
>
> v4: add missing patch
> v3: squash fixup patch
> v2: rebased
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Uma Shankar <uma.shankar@intel.com>
>
> Jouni Högander (4):
> drm/xe: Add empty def for i915_gem_object_flush_if_display
> Revert "FIXME: drm/i915: More display ugly wa needed after rebase"
> drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base
> fixup! FIXME: drm/i915/display: Remaining changes to make xe compile
>
> drivers/gpu/drm/i915/display/intel_fb.c | 10 ++--------
> drivers/gpu/drm/i915/display/intel_frontbuffer.c | 2 --
> drivers/gpu/drm/xe/xe_bo.h | 2 ++
> 3 files changed, 4 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2023-10-04 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 10:23 [Intel-xe] [PATCH v4 0/4] Frontbuffer tracking and dirtyfb Jouni Högander
2023-10-02 10:23 ` [Intel-xe] [PATCH v4 1/4] drm/xe: Add empty def for i915_gem_object_flush_if_display Jouni Högander
2023-10-02 10:23 ` [Intel-xe] [PATCH v4 2/4] Revert "FIXME: drm/i915: More display ugly wa needed after rebase" Jouni Högander
2023-10-02 10:23 ` [Intel-xe] [PATCH v4 3/4] drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base Jouni Högander
2023-10-02 10:23 ` [Intel-xe] [PATCH v4 4/4] fixup! FIXME: drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-10-02 13:53 ` [Intel-xe] ✓ CI.Patch_applied: success for Frontbuffer tracking and dirtyfb (rev4) Patchwork
2023-10-02 13:53 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-02 13:54 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-04 16:21 ` Maarten Lankhorst [this message]
2023-10-05 6:48 ` [Intel-xe] [PATCH v4 0/4] Frontbuffer tracking and dirtyfb Hogander, Jouni
2023-10-05 5:27 ` [Intel-xe] ✓ CI.Patch_applied: success for Frontbuffer tracking and dirtyfb (rev5) Patchwork
2023-10-05 5:27 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-05 5:29 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-05 5:36 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-05 5:36 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-05 5:37 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-05 6:15 ` [Intel-xe] ✓ CI.BAT: success " 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=9d2a6f00-14ad-41db-98bb-caaba43f70f5@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jouni.hogander@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox