From: Andi Shyti <andi.shyti@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915/ttm: implement access_memory
Date: Mon, 3 Oct 2022 22:42:27 +0200 [thread overview]
Message-ID: <YztJM1JtEwWcaIz0@ashyti-mobl2.lan> (raw)
In-Reply-To: <20221003172819.99245-1-matthew.auld@intel.com>
Hi Matt,
On Mon, Oct 03, 2022 at 06:28:19PM +0100, Matthew Auld wrote:
> It looks like we need this for local-memory, if we want to use ptrace.
> Something more is still needed if we want to handle non-mappable memory,
> which looks quite annoying.
>
> v2:
> - ttm_bo_kmap doesn't seem to work well here, and seems to expect
> contiguous resource.
> v3(Andi):
> - s/PAGE_SIZE/bytes/ when passing in the size of the mapping.
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/6989
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thanks,
Andi
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 45 +++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> index 3dc6acfcf4ec..d11cd9c57247 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
> @@ -699,6 +699,50 @@ static unsigned long i915_ttm_io_mem_pfn(struct ttm_buffer_object *bo,
> return ((base + sg_dma_address(sg)) >> PAGE_SHIFT) + ofs;
> }
>
> +static int i915_ttm_access_memory(struct ttm_buffer_object *bo,
> + unsigned long offset, void *buf,
> + int len, int write)
> +{
> + struct drm_i915_gem_object *obj = i915_ttm_to_gem(bo);
> + resource_size_t iomap = obj->mm.region->iomap.base -
> + obj->mm.region->region.start;
> + unsigned long page = offset >> PAGE_SHIFT;
> + unsigned long bytes_left = len;
> +
> + /*
> + * TODO: For now just let it fail if the resource is non-mappable,
> + * otherwise we need to perform the memcpy from the gpu here, without
> + * interfering with the object (like moving the entire thing).
> + */
> + if (!i915_ttm_resource_mappable(bo->resource))
> + return -EIO;
> +
> + offset -= page << PAGE_SHIFT;
> + do {
> + unsigned long bytes = min(bytes_left, PAGE_SIZE - offset);
> + void __iomem *ptr;
> + dma_addr_t daddr;
> +
> + daddr = i915_gem_object_get_dma_address(obj, page);
> + ptr = ioremap_wc(iomap + daddr + offset, bytes);
> + if (!ptr)
> + return -EIO;
> +
> + if (write)
> + memcpy_toio(ptr, buf, bytes);
> + else
> + memcpy_fromio(buf, ptr, bytes);
> + iounmap(ptr);
> +
> + page++;
> + buf += bytes;
> + bytes_left -= bytes;
> + offset = 0;
> + } while (bytes_left);
> +
> + return len;
> +}
> +
> /*
> * All callbacks need to take care not to downcast a struct ttm_buffer_object
> * without checking its subclass, since it might be a TTM ghost object.
> @@ -715,6 +759,7 @@ static struct ttm_device_funcs i915_ttm_bo_driver = {
> .delete_mem_notify = i915_ttm_delete_mem_notify,
> .io_mem_reserve = i915_ttm_io_mem_reserve,
> .io_mem_pfn = i915_ttm_io_mem_pfn,
> + .access_memory = i915_ttm_access_memory,
> };
>
> /**
> --
> 2.37.3
next prev parent reply other threads:[~2022-10-03 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:28 [Intel-gfx] [PATCH v3] drm/i915/ttm: implement access_memory Matthew Auld
2022-10-03 20:42 ` Andi Shyti [this message]
2022-10-03 23:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ttm: implement access_memory (rev3) Patchwork
2022-10-04 5:32 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=YztJM1JtEwWcaIz0@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@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