Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v2] drm/xe/display: fix ttm_bo_access() usage
Date: Mon, 02 Dec 2024 18:05:02 +0100	[thread overview]
Message-ID: <b9839a511b8b4a4c5425b63c23444788fb8b0fca.camel@linux.intel.com> (raw)
In-Reply-To: <20241202170102.88893-2-matthew.auld@intel.com>

On Mon, 2024-12-02 at 17:01 +0000, Matthew Auld wrote:
> ttm_bo_access() returns the size on success. Account for that
> otherwise
> the caller incorrectly thinks this is an error in
> intel_atomic_prepare_plane_clear_colors().
> 
> v2 (Thomas)
>  - Make sure we check for the partial copy case. Also since this api
> is
>    easy to get wrong, wrap the whole thing in a new helper to hide
> the
>    details and then convert the existing users over.
> 
> Fixes: b6308aaa24a7 ("drm/xe/display: Update intel_bo_read_from_page
> to use ttm_bo_access")
> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/3661
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>

> ---
>  drivers/gpu/drm/xe/display/intel_bo.c |  2 +-
>  drivers/gpu/drm/xe/xe_bo.c            | 24 ++++++++++++++++++++++++
>  drivers/gpu/drm/xe/xe_bo.h            |  1 +
>  drivers/gpu/drm/xe/xe_vm.c            |  8 ++------
>  4 files changed, 28 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/display/intel_bo.c
> b/drivers/gpu/drm/xe/display/intel_bo.c
> index 43141964f6f2..b463f5bd4eed 100644
> --- a/drivers/gpu/drm/xe/display/intel_bo.c
> +++ b/drivers/gpu/drm/xe/display/intel_bo.c
> @@ -41,7 +41,7 @@ int intel_bo_read_from_page(struct drm_gem_object
> *obj, u64 offset, void *dst, i
>  {
>  	struct xe_bo *bo = gem_to_xe_bo(obj);
>  
> -	return ttm_bo_access(&bo->ttm, offset, dst, size, 0);
> +	return xe_bo_read(bo, offset, dst, size);
>  }
>  
>  struct intel_frontbuffer *intel_bo_get_frontbuffer(struct
> drm_gem_object *obj)
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index f51d86511cb9..af85e5b8895f 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -1320,6 +1320,30 @@ static int xe_bo_vm_access(struct
> vm_area_struct *vma, unsigned long addr,
>  	return ret;
>  }
>  
> +/**
> + * xe_bo_read() - Read from an xe_bo
> + * @bo: The buffer object to read from.
> + * @offset: The byte offset to start reading from.
> + * @dst: Location to store the read.
> + * @size: Size in bytes for the read.
> +
> + * Read @size bytes from the @bo, starting from @offset, storing
> into @dst.
> + *
> + * Return: Zero on success, or negative error.
> + */
> +int xe_bo_read(struct xe_bo *bo, u64 offset, void *dst, int size)
> +{
> +	int ret;
> +
> +	ret = ttm_bo_access(&bo->ttm, offset, dst, size, 0);
> +	if (ret >= 0 && ret != size)
> +		ret = -EIO;
> +	else if (ret == size)
> +		ret = 0;
> +
> +	return ret;
> +}
> +
>  static const struct vm_operations_struct xe_gem_vm_ops = {
>  	.fault = xe_gem_fault,
>  	.open = ttm_bo_vm_open,
> diff --git a/drivers/gpu/drm/xe/xe_bo.h b/drivers/gpu/drm/xe/xe_bo.h
> index d0dce44317c7..d9386ab03140 100644
> --- a/drivers/gpu/drm/xe/xe_bo.h
> +++ b/drivers/gpu/drm/xe/xe_bo.h
> @@ -228,6 +228,7 @@ xe_bo_ggtt_addr(struct xe_bo *bo)
>  
>  int xe_bo_vmap(struct xe_bo *bo);
>  void xe_bo_vunmap(struct xe_bo *bo);
> +int xe_bo_read(struct xe_bo *bo, u64 offset, void *dst, int size);
>  
>  bool mem_type_is_vram(u32 mem_type);
>  bool xe_bo_is_vram(struct xe_bo *bo);
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 2492750505d6..7788680da4e5 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -3321,12 +3321,8 @@ void xe_vm_snapshot_capture_delayed(struct
> xe_vm_snapshot *snap)
>  		}
>  
>  		if (bo) {
> -			err = ttm_bo_access(&bo->ttm, snap-
> >snap[i].bo_ofs,
> -					    snap->snap[i].data,
> snap->snap[i].len, 0);
> -			if (!(err < 0) && err != snap->snap[i].len)
> -				err = -EIO;
> -			else if (!(err < 0))
> -				err = 0;
> +			err = xe_bo_read(bo, snap->snap[i].bo_ofs,
> +					 snap->snap[i].data, snap-
> >snap[i].len);
>  		} else {
>  			void __user *userptr = (void __user
> *)(size_t)snap->snap[i].bo_ofs;
>  


  reply	other threads:[~2024-12-02 17:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 17:01 [PATCH v2] drm/xe/display: fix ttm_bo_access() usage Matthew Auld
2024-12-02 17:05 ` Thomas Hellström [this message]
2024-12-02 17:28 ` ✓ CI.Patch_applied: success for drm/xe/display: fix ttm_bo_access() usage (rev2) Patchwork
2024-12-02 17:28 ` ✓ CI.checkpatch: " Patchwork
2024-12-02 17:29 ` ✓ CI.KUnit: " Patchwork
2024-12-02 17:47 ` ✓ CI.Build: " Patchwork
2024-12-02 17:50 ` ✗ CI.Hooks: failure " Patchwork
2024-12-02 17:51 ` ✓ CI.checksparse: success " Patchwork
2024-12-02 18:22 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-02 19:31 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-03 15:08 ` ✓ CI.Patch_applied: success for drm/xe/display: fix ttm_bo_access() usage (rev3) Patchwork
2024-12-03 15:08 ` ✓ CI.checkpatch: " Patchwork
2024-12-03 15:10 ` ✓ CI.KUnit: " Patchwork
2024-12-03 15:15 ` [PATCH v2] drm/xe/display: fix ttm_bo_access() usage Nirmoy Das
2024-12-03 15:28 ` ✓ CI.Build: success for drm/xe/display: fix ttm_bo_access() usage (rev3) Patchwork
2024-12-03 15:30 ` ✗ CI.Hooks: failure " Patchwork
2024-12-03 15:32 ` ✓ CI.checksparse: success " Patchwork
2024-12-03 16:37 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-03 18:41 ` ✗ Xe.CI.Full: 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=b9839a511b8b4a4c5425b63c23444788fb8b0fca.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@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