From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [Intel-xe] [RFC PATCH 14/20] drm/xe: Add function to clear scanout flag
Date: Fri, 5 May 2023 10:43:41 +0200 [thread overview]
Message-ID: <88a16b59-e26b-26ef-1601-a380f2cda6ed@linux.intel.com> (raw)
In-Reply-To: <20230505082956.2247875-15-jouni.hogander@intel.com>
Hey,
We don't clear scanout on Xe, it should be set only once by userspace as
a flag to determine caching mode
for VM_BIND, it shouldn't ever be cleared in xe display code.
~Maarten
On 2023-05-05 10:29, Jouni Högander wrote:
> Add function to clear scanout flag. This will be called by frontbuffer
> tracking code.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h b/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
> index c40bb27ac72a..dec11721ef6a 100644
> --- a/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
> +++ b/drivers/gpu/drm/xe/compat-i915-headers/i915_vma.h
> @@ -4,11 +4,22 @@
> #include <uapi/drm/i915_drm.h>
> #include <drm/drm_mm.h>
>
> -struct xe_bo;
> +#include <xe_bo.h>
> +#include <xe_bo_types.h>
>
> struct i915_vma {
> struct xe_bo *bo, *dpt;
> struct drm_mm_node node;
> };
>
> +static inline void i915_ggtt_clear_scanout(struct xe_bo *bo)
> +{
> + int ret;
> +
> + ret = ttm_bo_reserve(&bo->ttm, true, false, NULL);
> + XE_WARN_ON(ret);
> + bo->flags &= ~XE_BO_SCANOUT_BIT;
> + ttm_bo_unreserve(&bo->ttm);
> +}
> +
> #endif
next prev parent reply other threads:[~2023-05-05 8:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:29 [Intel-xe] [RFC PATCH 00/20] Xe frontbuffer tracking Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 01/20] Revert "drm/i915/display: Neuter frontbuffer tracking harder" Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 02/20] Revert "drm/i915: Remove gem and overlay frontbuffer tracking" Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 03/20] fixup! drm/i915/display: Remaining changes to make xe compile Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 04/20] fixup! drm/xe/display: Implement display support Jouni Högander
2023-05-05 14:44 ` Rodrigo Vivi
2023-05-08 9:19 ` Hogander, Jouni
2023-05-08 13:35 ` Rodrigo Vivi
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 05/20] drm/i915/display: Change __intel_frontbuffer_get parameter Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 06/20] drm/i915: Add macros to get i915 device from i915_gem_object Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 07/20] drm/xe: Add macro to get i915 device from xe_bo Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 08/20] drm/xe: Add intel_bo_flush_if_display define for Xe Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 09/20] drm/i915: Add intel_bo_flush_if_display define for i915 Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 10/20] drm/xe: Add struct i915_active for Xe Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 11/20] drm/xe: Add i915_active.h compatibility header Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 12/20] drm/xe/display: Include i916_active related headers Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 13/20] drm/i915: Add function to clear scanout flag for vmas Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 14/20] drm/xe: Add function to clear scanout flag Jouni Högander
2023-05-05 8:43 ` Maarten Lankhorst [this message]
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 15/20] drm/i915/display: Use i915_ggtt_clear_scanout Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 16/20] drm/i915/display: Use drm_gem_object_get/put Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 17/20] drm/xe/display: Use frontbuffer tracking for Xe as well Jouni Högander
2023-05-05 8:50 ` Maarten Lankhorst
2023-05-05 11:39 ` Hogander, Jouni
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 18/20] drm/i915: Add new frontbuffer tracking interface to queue flush Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 19/20] drm/i915: Handle dma fences in dirtyfb callback Jouni Högander
2023-05-05 8:29 ` [Intel-xe] [RFC PATCH 20/20] drm/xe/display: Use custom dirtyfb for Xe as well Jouni Högander
2023-05-05 8:34 ` [Intel-xe] ✓ CI.Patch_applied: success for Xe frontbuffer tracking Patchwork
2023-05-05 8:35 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-05 8:38 ` [Intel-xe] ✗ CI.Build: failure " 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=88a16b59-e26b-26ef-1601-a380f2cda6ed@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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox