From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
Chris Wilson <chris.p.wilson@linux.intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Sima <daniel.vetter@ffwll.ch>,
Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v2 0/2] Allow partial memory mapping for cpu memory
Date: Wed, 14 Aug 2024 15:51:51 +0200 [thread overview]
Message-ID: <Zry2d2LtQLiPY58x@ashyti-mobl2.lan> (raw)
In-Reply-To: <20240814134837.116498-1-andi.shyti@linux.intel.com>
Argh... sorry, I messed up with format-patch and send-mail and
sent it twice.
Maybe I need to resend it if CI complains.
Andi
On Wed, Aug 14, 2024 at 03:48:32PM +0200, Andi Shyti wrote:
> Hi,
>
> I am resending this patch series, not to disregard the previous
> discussions, but to ensure it gets tested with the IGTs that
> Krzysztof has provided.
>
> This patch series finalizes the memory mapping fixes and
> improvements by enabling partial memory mapping for CPU memory as
> well.
>
> The concept of partial memory mapping, achieved by adding an
> object offset, was implicitly introduced in commit 8bdd9ef7e9b1
> ("drm/i915/gem: Fix Virtual Memory mapping boundaries
> calculation") for GTT memory.
>
> To address a previous discussion with Sima and Matt, this feature
> is used by Mesa and is required across all platforms utilizing
> Mesa. Although Nirmoy suggested using the Fixes tag to backport
> this to previous kernels, I view this as a new feature rather
> than a fix.
>
> Lionel, please let me know if you have a different perspective
> and believe this should be treated as a bug fix, requiring it
> to be backported to stable kernels.
>
> The IGTs have been developed in collaboration with the Mesa team
> to replicate the exact Mesa use case[*].
>
> Thanks Chris for the support, thanks Krzysztof for taking care of
> the IGT tests, thanks Nirmoy for your reviews and thanks Sima and
> Matt for the discussion on this series.
>
> Andi
>
> [*] https://patchwork.freedesktop.org/patch/608232/?series=137303&rev=1
>
> Test-with: 20240814132404.18392-1-krzysztof.niemiec@intel.com
>
> Changelog:
> ==========
> v1 -> v2
> - Added Nirmoy's tags.
>
> Andi Shyti (2):
> 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 | 10 ++++++----
> drivers/gpu/drm/i915/i915_mm.c | 12 +++++++++++-
> drivers/gpu/drm/i915/i915_mm.h | 3 ++-
> 3 files changed, 19 insertions(+), 6 deletions(-)
>
> --
> 2.45.2
next prev parent reply other threads:[~2024-08-14 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 13:48 [PATCH v2 0/2] Allow partial memory mapping for cpu memory Andi Shyti
2024-08-14 13:48 ` [PATCH v2 1/2] drm/i915/gem: Do not look for the exact address in node Andi Shyti
2024-08-14 13:48 ` [PATCH v2 2/2] drm/i915/gem: Calculate object page offset for partial memory mapping Andi Shyti
2024-08-14 13:48 ` [PATCH v2 0/2] Allow partial memory mapping for cpu memory Andi Shyti
2024-08-14 13:48 ` [PATCH v2 1/2] drm/i915/gem: Do not look for the exact address in node Andi Shyti
2024-08-14 13:48 ` [PATCH v2 2/2] drm/i915/gem: Calculate object page offset for partial memory mapping Andi Shyti
2024-08-14 13:51 ` Andi Shyti [this message]
2024-08-14 14:49 ` ✓ Fi.CI.BAT: success for Allow partial memory mapping for cpu memory Patchwork
2024-08-14 16:07 ` [PATCH v2 0/2] " Matthew Brost
2024-08-19 15:16 ` Andi Shyti
2024-08-19 16:53 ` Matthew Brost
2024-08-22 9:49 ` Daniel Vetter
2024-08-14 18:29 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-08-14 22:12 ` ✓ Fi.CI.BAT: success for Allow partial memory mapping for cpu memory (rev2) Patchwork
2024-08-16 5:25 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-08-14 13:47 [PATCH v2 0/2] Allow partial memory mapping for cpu memory Andi Shyti
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=Zry2d2LtQLiPY58x@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.niemiec@intel.com \
--cc=lionel.g.landwerlin@intel.com \
--cc=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.