From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 1/4] drm/i915: Add macros to get i915 device from i915_gem_object
Date: Mon, 31 Jul 2023 11:32:13 +0200 [thread overview]
Message-ID: <b9e456d0-1b46-05ff-4054-3f79dbf7de21@linux.intel.com> (raw)
In-Reply-To: <20230727064142.751976-2-jouni.hogander@intel.com>
On 7/27/2023 8:41 AM, Jouni Högander wrote:
> We want to stop touching directly i915_gem_object struct members in
> intel_frontbuffer code. As a part of this we add helper macro to get i915
> device from i915_gem_object.
>
> v2: operate on and return pointer in defined macros
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> .../gpu/drm/i915/display/intel_frontbuffer.c | 18 +++++++++---------
> .../gpu/drm/i915/gem/i915_gem_object_types.h | 3 +++
> 2 files changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.c b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> index 17a7aa8b28c2..3ce0436a0c7d 100644
> --- a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> +++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> @@ -167,7 +167,7 @@ void __intel_fb_invalidate(struct intel_frontbuffer *front,
> enum fb_op_origin origin,
> unsigned int frontbuffer_bits)
> {
> - struct drm_i915_private *i915 = to_i915(front->obj->base.dev);
> + struct drm_i915_private *i915 = intel_bo_to_i915(front->obj);
>
> if (origin == ORIGIN_CS) {
> spin_lock(&i915->display.fb_tracking.lock);
> @@ -188,7 +188,7 @@ void __intel_fb_flush(struct intel_frontbuffer *front,
> enum fb_op_origin origin,
> unsigned int frontbuffer_bits)
> {
> - struct drm_i915_private *i915 = to_i915(front->obj->base.dev);
> + struct drm_i915_private *i915 = intel_bo_to_i915(front->obj);
>
> if (origin == ORIGIN_CS) {
> spin_lock(&i915->display.fb_tracking.lock);
> @@ -221,14 +221,14 @@ static void frontbuffer_retire(struct i915_active *ref)
> }
>
> static void frontbuffer_release(struct kref *ref)
> - __releases(&to_i915(front->obj->base.dev)->display.fb_tracking.lock)
> + __releases(&intel_bo_to_i915(front->obj)->display.fb_tracking.lock)
> {
> struct intel_frontbuffer *front =
> container_of(ref, typeof(*front), ref);
> struct drm_i915_gem_object *obj = front->obj;
> struct i915_vma *vma;
>
> - drm_WARN_ON(obj->base.dev, atomic_read(&front->bits));
> + drm_WARN_ON(&intel_bo_to_i915(obj)->drm, atomic_read(&front->bits));
>
> spin_lock(&obj->vma.lock);
> for_each_ggtt_vma(vma, obj) {
> @@ -238,7 +238,7 @@ static void frontbuffer_release(struct kref *ref)
> spin_unlock(&obj->vma.lock);
>
> RCU_INIT_POINTER(obj->frontbuffer, NULL);
> - spin_unlock(&to_i915(obj->base.dev)->display.fb_tracking.lock);
> + spin_unlock(&intel_bo_to_i915(obj)->display.fb_tracking.lock);
>
> i915_active_fini(&front->write);
>
> @@ -249,7 +249,7 @@ static void frontbuffer_release(struct kref *ref)
> struct intel_frontbuffer *
> intel_frontbuffer_get(struct drm_i915_gem_object *obj)
> {
> - struct drm_i915_private *i915 = to_i915(obj->base.dev);
> + struct drm_i915_private *i915 = intel_bo_to_i915(obj);
> struct intel_frontbuffer *front;
>
> front = __intel_frontbuffer_get(obj);
> @@ -286,7 +286,7 @@ void intel_frontbuffer_put(struct intel_frontbuffer *front)
> {
> kref_put_lock(&front->ref,
> frontbuffer_release,
> - &to_i915(front->obj->base.dev)->display.fb_tracking.lock);
> + &intel_bo_to_i915(front->obj)->display.fb_tracking.lock);
> }
>
> /**
> @@ -315,13 +315,13 @@ void intel_frontbuffer_track(struct intel_frontbuffer *old,
> BUILD_BUG_ON(I915_MAX_PLANES > INTEL_FRONTBUFFER_BITS_PER_PIPE);
>
> if (old) {
> - drm_WARN_ON(old->obj->base.dev,
> + drm_WARN_ON(&intel_bo_to_i915(old->obj)->drm,
> !(atomic_read(&old->bits) & frontbuffer_bits));
> atomic_andnot(frontbuffer_bits, &old->bits);
> }
>
> if (new) {
> - drm_WARN_ON(new->obj->base.dev,
> + drm_WARN_ON(&intel_bo_to_i915(new->obj)->drm,
> atomic_read(&new->bits) & frontbuffer_bits);
> atomic_or(frontbuffer_bits, &new->bits);
> }
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object_types.h b/drivers/gpu/drm/i915/gem/i915_gem_object_types.h
> index e72c57716bee..3de7db70f4ed 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_object_types.h
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_object_types.h
> @@ -718,6 +718,9 @@ struct drm_i915_gem_object {
> };
> };
>
> +#define intel_bo_to_drm_bo(bo) (&(bo)->base)
> +#define intel_bo_to_i915(bo) to_i915(intel_bo_to_drm_bo(bo)->dev)
> +
> static inline struct drm_i915_gem_object *
> to_intel_bo(struct drm_gem_object *gem)
> {
next prev parent reply other threads:[~2023-07-31 9:32 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 [this message]
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 ` [Intel-gfx] [PATCH v4 0/4] Do not access i915_gem_object members from frontbuffer tracking Hogander, Jouni
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=b9e456d0-1b46-05ff-4054-3f79dbf7de21@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-gfx@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