From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH v3 0/4] Do not access i915_gem_object members from frontbuffer tracking
Date: Wed, 7 Jun 2023 11:12:23 +0300 [thread overview]
Message-ID: <20230607081227.96992-1-jouni.hogander@intel.com> (raw)
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.
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 | 44 +++++--------
.../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 | 66 +++++++++++++++++++
.../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, 110 insertions(+), 59 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-07 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 8:12 Jouni Högander [this message]
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 1/4] drm/i915: Add macros to get i915 device from i915_gem_object Jouni Högander
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 2/4] drm/i915: Add getter/setter for i915_gem_object->frontbuffer Jouni Högander
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 3/4] drm/i915/display: Remove i915_gem_object_types.h from intel_frontbuffer.h Jouni Högander
2023-06-07 8:12 ` [Intel-gfx] [PATCH v3 4/4] drm/i915: Add function to clear scanout flag for vmas Jouni Högander
2023-06-07 9:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Do not access i915_gem_object members from frontbuffer tracking (rev3) Patchwork
2023-06-07 10:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 21:47 ` [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=20230607081227.96992-1-jouni.hogander@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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