Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: 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@linux.intel.com>,
	Andi Shyti <andi.shyti@kernel.org>
Subject: [PATCH v3 0/3] Add support for partial mapping
Date: Fri, 12 Apr 2024 02:48:05 +0200	[thread overview]
Message-ID: <20240412004808.288130-1-andi.shyti@linux.intel.com> (raw)

Hi,

this series based on a previous work from Chris adds support for
partial mapping.

Two preparatory patches are needed:

 - set the vm_pgoff when mapping frame buffer objects
 - do not fail when the exact address of a VM node is not the
   same as the starting address due to the offset.

Indeed I was receiving a negative offset at first.

Igt tests have been sent to the igt mailing list.

Andi

Test-with: 20240412004255.288046-1-andi.shyti@linux.intel.com

Changelog:
==========
v2 -> v3:
 - Add a patch in order to not fail when the exact address of a
   VM node is not the same as the starting address due to the
   offset.

v1 -> v2:
 - Enable support for CPU memory
 - Increment vm_pgoff for fb objects

Andi Shyti (3):
  drm/i915/gem: Increment vma offset when mapping fb objects
  drm/i915/gem: Do not look for the exact address in node
  drm/i915/gem: Calculate object page offset for partial memory mapping

 drivers/gpu/drm/i915/gem/i915_gem_mman.c | 18 ++++++++++++------
 drivers/gpu/drm/i915/i915_mm.c           | 12 +++++++++++-
 drivers/gpu/drm/i915/i915_mm.h           |  3 ++-
 3 files changed, 25 insertions(+), 8 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-04-12  0:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  0:48 Andi Shyti [this message]
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
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=20240412004808.288130-1-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --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