From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Chris Wilson <chris.p.wilson@linux.intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH v3 1/3] drm/i915/gem: Increment vma offset when mapping fb objects
Date: Tue, 23 Apr 2024 11:17:04 +0200 [thread overview]
Message-ID: <dec83fc1-def8-4005-9f0d-dad4dc2f17b1@linux.intel.com> (raw)
In-Reply-To: <20240412004808.288130-2-andi.shyti@linux.intel.com>
Hi Andi,
On 4/12/2024 2:48 AM, Andi Shyti wrote:
> Until now the "vm_pgoff" was not used and there has been no need
> to set its offset.
>
> But now, because we want to support partial mappings with a given
> offset, we need it to be set.
>
> Suggested-by: Chris Wilson <chris.p.wilson@linux.intel.com>
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
Do we have a IGT for partial FB mmap test ? Would be nice to have one
but this patch looks good to me.
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Regards,
Nirmoy
> ---
> drivers/gpu/drm/i915/gem/i915_gem_mman.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_mman.c b/drivers/gpu/drm/i915/gem/i915_gem_mman.c
> index a2195e28b625..ce10dd259812 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_mman.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_mman.c
> @@ -1084,6 +1084,8 @@ int i915_gem_fb_mmap(struct drm_i915_gem_object *obj, struct vm_area_struct *vma
> mmo = mmap_offset_attach(obj, mmap_type, NULL);
> if (IS_ERR(mmo))
> return PTR_ERR(mmo);
> +
> + vma->vm_pgoff += drm_vma_node_start(&mmo->vma_node);
> }
>
> /*
next prev parent reply other threads:[~2024-04-23 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 0:48 [PATCH v3 0/3] Add support for partial mapping Andi Shyti
2024-04-12 0:48 ` [PATCH v3 1/3] drm/i915/gem: Increment vma offset when mapping fb objects Andi Shyti
2024-04-23 9:17 ` Nirmoy Das [this message]
2024-04-12 0:48 ` [PATCH v3 2/3] drm/i915/gem: Do not look for the exact address in node Andi Shyti
2024-04-12 0:48 ` [PATCH v3 3/3] drm/i915/gem: Calculate object page offset for partial memory mapping Andi Shyti
2024-04-12 1:27 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for partial mapping (rev4) Patchwork
2024-04-12 1:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-15 9:19 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for partial mapping (rev5) Patchwork
2024-04-15 9:35 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-15 12:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-15 23:12 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for partial mapping (rev6) Patchwork
2024-04-15 23:20 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-16 9:36 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-16 12:19 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for partial mapping (rev7) Patchwork
2024-04-16 12:34 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-17 9:00 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for partial mapping (rev8) Patchwork
2024-04-17 9:07 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-17 13:25 ` ✗ 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=dec83fc1-def8-4005-9f0d-dad4dc2f17b1@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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