From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 07/10] drm/{i915,xe}/fbdev: add intel_fbdev_fb_bo_destroy()
Date: Thu, 18 Sep 2025 20:43:33 +0300 [thread overview]
Message-ID: <aMxExfraYUfQh3QZ@intel.com> (raw)
In-Reply-To: <22bc3c3158f5a22ab258ada8684766fdf75fefec.1758184771.git.jani.nikula@intel.com>
On Thu, Sep 18, 2025 at 11:40:57AM +0300, Jani Nikula wrote:
> i915 and xe do different things on the failure path; i915 calls
> drm_gem_object_put() while xe calls xe_bo_unpin_map_no_vm(). Add a
> helper to enable further refactoring.
>
> v2: Call drm_gem_object_put() on intel_fbdev_fb_bo_destroy()
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fbdev_fb.c | 7 ++++++-
> drivers/gpu/drm/i915/display/intel_fbdev_fb.h | 1 +
> drivers/gpu/drm/xe/display/intel_fbdev_fb.c | 7 ++++++-
> 3 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev_fb.c b/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> index bfd05fd34348..a7dab8cd3aa2 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev_fb.c
> @@ -46,6 +46,11 @@ struct drm_gem_object *intel_fbdev_fb_bo_create(struct drm_device *drm, int size
> return &obj->base;
> }
>
> +void intel_fbdev_fb_bo_destroy(struct drm_gem_object *obj)
> +{
> + drm_gem_object_put(obj);
> +}
> +
> struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_device *drm,
> struct drm_mode_fb_cmd2 *mode_cmd)
> {
> @@ -68,7 +73,7 @@ struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_device *drm,
> mode_cmd->modifier[0]),
> mode_cmd);
> if (IS_ERR(fb)) {
> - drm_gem_object_put(obj);
> + intel_fbdev_fb_bo_destroy(obj);
> goto err;
> }
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev_fb.h b/drivers/gpu/drm/i915/display/intel_fbdev_fb.h
> index 6a4ba40d5831..8b6214b0ad0e 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev_fb.h
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev_fb.h
> @@ -14,6 +14,7 @@ struct i915_vma;
> struct intel_display;
>
> struct drm_gem_object *intel_fbdev_fb_bo_create(struct drm_device *drm, int size);
> +void intel_fbdev_fb_bo_destroy(struct drm_gem_object *obj);
> struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_device *drm,
> struct drm_mode_fb_cmd2 *mode_cmd);
> int intel_fbdev_fb_fill_info(struct intel_display *display, struct fb_info *info,
> diff --git a/drivers/gpu/drm/xe/display/intel_fbdev_fb.c b/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> index 48225062211c..defbab3df55b 100644
> --- a/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> +++ b/drivers/gpu/drm/xe/display/intel_fbdev_fb.c
> @@ -49,6 +49,11 @@ struct drm_gem_object *intel_fbdev_fb_bo_create(struct drm_device *drm, int size
> return &obj->ttm.base;
> }
>
> +void intel_fbdev_fb_bo_destroy(struct drm_gem_object *obj)
> +{
> + xe_bo_unpin_map_no_vm(gem_to_xe_bo(obj));
> +}
> +
> struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_device *drm,
> struct drm_mode_fb_cmd2 *mode_cmd)
> {
> @@ -71,7 +76,7 @@ struct intel_framebuffer *intel_fbdev_fb_alloc(struct drm_device *drm,
> mode_cmd->modifier[0]),
> mode_cmd);
> if (IS_ERR(fb)) {
> - xe_bo_unpin_map_no_vm(gem_to_xe_bo(obj));
> + intel_fbdev_fb_bo_destroy(obj);
> goto err;
> }
>
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-09-18 17:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 8:40 [PATCH v2 00/10] drm/{i915,xe}/fbdev: refactor Jani Nikula
2025-09-18 8:40 ` [PATCH v2 01/10] drm/xe/fbdev: use the same 64-byte stride alignment as i915 Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 02/10] drm/i915/fbdev: make intel_framebuffer_create() error return handling explicit Jani Nikula
2025-09-18 17:38 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 03/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_alloc() Jani Nikula
2025-09-18 17:39 ` [PATCH v2 03/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 04/10] drm/{i915, xe}/fbdev: deduplicate struct drm_mode_fb_cmd2 init Jani Nikula
2025-09-18 17:40 ` [PATCH v2 04/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 05/10] drm/i915/fbdev: abstract bo creation Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 06/10] drm/xe/fbdev: " Jani Nikula
2025-09-18 17:42 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 07/10] drm/{i915, xe}/fbdev: add intel_fbdev_fb_bo_destroy() Jani Nikula
2025-09-18 17:43 ` Ville Syrjälä [this message]
2025-09-18 8:40 ` [PATCH v2 08/10] drm/{i915,xe}/fbdev: deduplicate fbdev creation Jani Nikula
2025-09-18 17:44 ` Ville Syrjälä
2025-09-18 8:40 ` [PATCH v2 09/10] drm/{i915, xe}/fbdev: pass struct drm_device to intel_fbdev_fb_fill_info() Jani Nikula
2025-09-18 17:45 ` [PATCH v2 09/10] drm/{i915,xe}/fbdev: " Ville Syrjälä
2025-09-18 8:41 ` [PATCH v2 10/10] drm/i915/fbdev: drop dependency on display in i915 specific code Jani Nikula
2025-09-18 17:50 ` Ville Syrjälä
2025-09-19 7:00 ` Jani Nikula
2025-09-18 8:59 ` ✓ CI.KUnit: success for drm/{i915,xe}/fbdev: refactor (rev2) Patchwork
2025-09-18 9:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 15:54 ` ✓ Xe.CI.Full: " 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=aMxExfraYUfQh3QZ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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