From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Das, Nirmoy" <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 0/4] Do not access i915_gem_object members from frontbuffer tracking
Date: Tue, 1 Aug 2023 07:04:24 +0000 [thread overview]
Message-ID: <1f3c2ed6a4e4c3c92d68130981b9380606354215.camel@intel.com> (raw)
In-Reply-To: <20230727064142.751976-1-jouni.hogander@intel.com>
On Thu, 2023-07-27 at 09:41 +0300, Jouni Högander wrote:
> We are preparing for Xe driver. Binary objects will have differing
> implementation in Xe driver. Due this we want to remove direct
> accesses to i915_gem_object members and leave details to binary
> object
> implementation.
Thank you Nirmoy, Jani and Jeevan for reviews. This is now merged.
BR,
Jouni Högander
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
>
> v4:
> - Fix intel_frontbuffer_get return value
> - s/front_ret/cur/
> v3:
> - Move gem object frontbuffer getter/setter into header file
> - operate on and return pointer in defined macros
> v2: desribe i915_ggtt_clear_scanout function parameter
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> Jouni Högander (4):
> drm/i915: Add macros to get i915 device from i915_gem_object
> drm/i915: Add getter/setter for i915_gem_object->frontbuffer
> drm/i915/display: Remove i915_gem_object_types.h from
> intel_frontbuffer.h
> drm/i915: Add function to clear scanout flag for vmas
>
> .../gpu/drm/i915/display/intel_frontbuffer.c | 46 +++++--------
> .../gpu/drm/i915/display/intel_frontbuffer.h | 28 --------
> drivers/gpu/drm/i915/gem/i915_gem_object.c | 4 +-
> drivers/gpu/drm/i915/gem/i915_gem_object.h | 67
> +++++++++++++++++++
> .../gpu/drm/i915/gem/i915_gem_object_types.h | 3 +
> drivers/gpu/drm/i915/i915_vma.c | 22 +++++-
> drivers/gpu/drm/i915/i915_vma.h | 2 +
> 7 files changed, 112 insertions(+), 60 deletions(-)
>
prev parent reply other threads:[~2023-08-01 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 6:41 [Intel-gfx] [PATCH v4 0/4] Do not access i915_gem_object members from frontbuffer tracking Jouni Högander
2023-07-27 6:41 ` [Intel-gfx] [PATCH v4 1/4] drm/i915: Add macros to get i915 device from i915_gem_object Jouni Högander
2023-07-31 9:32 ` Nirmoy Das
2023-07-27 6:41 ` [Intel-gfx] [PATCH v4 2/4] drm/i915: Add getter/setter for i915_gem_object->frontbuffer Jouni Högander
2023-07-31 9:34 ` Nirmoy Das
2023-07-27 6:41 ` [Intel-gfx] [PATCH v4 3/4] drm/i915/display: Remove i915_gem_object_types.h from intel_frontbuffer.h Jouni Högander
2023-08-01 5:26 ` B, Jeevan
2023-07-27 6:41 ` [Intel-gfx] [PATCH v4 4/4] drm/i915: Add function to clear scanout flag for vmas Jouni Högander
2023-07-31 9:47 ` Nirmoy Das
2023-07-27 7:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do not access i915_gem_object members from frontbuffer tracking (rev4) Patchwork
2023-07-27 7:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-27 8:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-08-01 7:04 ` Hogander, Jouni [this message]
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=1f3c2ed6a4e4c3c92d68130981b9380606354215.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@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