From: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: kenneth.w.graunke@intel.com, sanjay.k.kumar@intel.com,
dri-devel@lists.freedesktop.org, jason.ekstrand@intel.com,
dave.hansen@intel.com, jglisse@redhat.com,
daniel.vetter@intel.com, dan.j.williams@intel.com,
ira.weiny@intel.com, jgg@mellanox.com
Subject: Re: [Intel-gfx] [RFC v2 00/12] drm/i915/svm: Add SVM support
Date: Fri, 24 Jan 2020 00:42:44 -0800 [thread overview]
Message-ID: <20200124084244.GD4253@nvishwa1-DESK.sc.intel.com> (raw)
In-Reply-To: <20191213215614.24558-1-niranjana.vishwanathapura@intel.com>
On Fri, Dec 13, 2019 at 01:56:02PM -0800, Niranjana Vishwanathapura wrote:
>Shared Virtual Memory (SVM) allows the programmer to use a single virtual
>address space which will be shared between threads executing on CPUs and GPUs.
>It abstracts away from the user the location of the backing memory, and hence
>simplifies the user programming model.
>SVM supports two types of virtual memory allocation methods.
>Runtime allocator requires the driver to provide memory allocation and
>management interface, like buffer object (BO) interface.
>Whereas system allocator makes use of default OS memory allocation and
>management support like malloc().
>
>This patch series adds both SVM system and runtime allocator support
>to i915 driver.
>
I will split runtime allocator and system allocator support into separate
RFC series. I will prioritize runtime allocator support to address the
feedback in patch [02] of this series.
Thanks,
Niranjana
>The patch series includes
> - SVM support for both system and runtime allocation.
> - Plugin in device memory with the Linux kernel.
> - User API advertising SVM capability and configuration by user on per
> vm basis.
> - User API to bind an address range or a BO with a device page table.
> - User API to prefetch an address range to device memory.
> - Implicit migration by moving pages or BOs back from device to host
> memory upon CPU access.
> - CPU copy and blitter copy support for migrating the pages/BOs.
> - Large page mapping support
> - Page table dump support.
>
>References:
>https://www.kernel.org/doc/Documentation/vm/hmm.rst
>The HMM use cases in the Linux kernel.
>Test RFC series
> "[RFC i-g-t 0/7] tests/i915/svm: Shared Virtual Memory (SVM) test"
>
>v2:
>- Use updated HMM API
>- HMM usage changes as per review feedback
>- UAPI name change as per review feedback
>- Reformat RFC series
>- Some minor fixes
>
>Niranjana Vishwanathapura (11):
> drm/i915/svm: Add SVM documentation
> drm/i915/svm: Runtime (RT) allocator support
> drm/i915/svm: Page table update support for SVM
> drm/i915/svm: Page table mirroring support
> drm/i915/svm: Device memory support
> drm/i915/svm: Implicitly migrate pages upon CPU fault
> drm/i915/svm: Page copy support during migration
> drm/i915/svm: Add functions to blitter copy SVM buffers
> drm/i915/svm: Use blitter copy for migration
> drm/i915/svm: Add support to en/disable SVM
> drm/i915/svm: Add page table dump support
>
>Venkata Sandeep Dhanalakota (1):
> drm/i915/svm: Implicitly migrate BOs upon CPU access
>
> Documentation/gpu/i915.rst | 29 +
> drivers/gpu/drm/i915/Kconfig | 23 +
> drivers/gpu/drm/i915/Kconfig.debug | 14 +
> drivers/gpu/drm/i915/Makefile | 6 +
> drivers/gpu/drm/i915/gem/i915_gem_context.c | 95 ++-
> drivers/gpu/drm/i915/gem/i915_gem_context.h | 2 +
> .../gpu/drm/i915/gem/i915_gem_context_types.h | 1 +
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 65 +-
> drivers/gpu/drm/i915/gem/i915_gem_mman.c | 10 +
> drivers/gpu/drm/i915/gem/i915_gem_object.c | 43 +-
> drivers/gpu/drm/i915/gem/i915_gem_object.h | 6 +
> drivers/gpu/drm/i915/gem/i915_gem_svm.c | 60 ++
> drivers/gpu/drm/i915/gem/i915_gem_svm.h | 22 +
> drivers/gpu/drm/i915/gem/i915_gem_wait.c | 2 +-
> drivers/gpu/drm/i915/i915_buddy.h | 12 +
> drivers/gpu/drm/i915/i915_drv.c | 31 +-
> drivers/gpu/drm/i915/i915_drv.h | 32 +
> drivers/gpu/drm/i915/i915_gem_gtt.c | 158 +++-
> drivers/gpu/drm/i915/i915_gem_gtt.h | 41 +
> drivers/gpu/drm/i915/i915_getparam.c | 3 +
> drivers/gpu/drm/i915/i915_svm.c | 330 ++++++++
> drivers/gpu/drm/i915/i915_svm.h | 71 ++
> drivers/gpu/drm/i915/i915_svm_copy.c | 172 ++++
> drivers/gpu/drm/i915/i915_svm_devmem.c | 781 ++++++++++++++++++
> drivers/gpu/drm/i915/intel_memory_region.c | 4 -
> drivers/gpu/drm/i915/intel_memory_region.h | 18 +
> drivers/gpu/drm/i915/intel_region_lmem.c | 10 +
> include/uapi/drm/i915_drm.h | 73 ++
> 28 files changed, 2078 insertions(+), 36 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_svm.c
> create mode 100644 drivers/gpu/drm/i915/gem/i915_gem_svm.h
> create mode 100644 drivers/gpu/drm/i915/i915_svm.c
> create mode 100644 drivers/gpu/drm/i915/i915_svm.h
> create mode 100644 drivers/gpu/drm/i915/i915_svm_copy.c
> create mode 100644 drivers/gpu/drm/i915/i915_svm_devmem.c
>
>--
>2.21.0.rc0.32.g243a4c7e27
>
>_______________________________________________
>dri-devel mailing list
>dri-devel@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-24 8:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 21:56 [Intel-gfx] [RFC v2 00/12] drm/i915/svm: Add SVM support Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 01/12] drm/i915/svm: Add SVM documentation Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 02/12] drm/i915/svm: Runtime (RT) allocator support Niranjana Vishwanathapura
2019-12-13 22:58 ` Jason Ekstrand
2019-12-13 23:13 ` Niranjan Vishwanathapura
2019-12-14 0:36 ` Jason Ekstrand
2019-12-14 10:31 ` Chris Wilson
2019-12-16 4:13 ` Niranjan Vishwanathapura
2019-12-17 18:01 ` Jason Ekstrand
2019-12-18 23:25 ` Niranjana Vishwanathapura
2019-12-14 10:56 ` Chris Wilson
2019-12-16 4:15 ` Niranjan Vishwanathapura
2019-12-18 22:51 ` Niranjana Vishwanathapura
2019-12-17 20:18 ` Jason Gunthorpe
2019-12-18 23:34 ` Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 03/12] drm/i915/svm: Implicitly migrate BOs upon CPU access Niranjana Vishwanathapura
2019-12-14 10:58 ` Chris Wilson
2019-12-16 4:17 ` Niranjan Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 04/12] drm/i915/svm: Page table update support for SVM Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 05/12] drm/i915/svm: Page table mirroring support Niranjana Vishwanathapura
2019-12-17 20:31 ` Jason Gunthorpe
2019-12-18 22:41 ` Niranjana Vishwanathapura
2019-12-20 13:45 ` Jason Gunthorpe
2019-12-22 19:54 ` Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 06/12] drm/i915/svm: Device memory support Niranjana Vishwanathapura
2019-12-17 20:35 ` Jason Gunthorpe
2019-12-18 22:15 ` Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 07/12] drm/i915/svm: Implicitly migrate pages upon CPU fault Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 08/12] drm/i915/svm: Page copy support during migration Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 09/12] drm/i915/svm: Add functions to blitter copy SVM buffers Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 10/12] drm/i915/svm: Use blitter copy for migration Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 11/12] drm/i915/svm: Add support to en/disable SVM Niranjana Vishwanathapura
2019-12-13 21:56 ` [Intel-gfx] [RFC v2 12/12] drm/i915/svm: Add page table dump support Niranjana Vishwanathapura
2019-12-14 1:32 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/svm: Add SVM support (rev2) Patchwork
2020-01-24 8:42 ` Niranjana Vishwanathapura [this message]
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=20200124084244.GD4253@nvishwa1-DESK.sc.intel.com \
--to=niranjana.vishwanathapura@intel.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dave.hansen@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ira.weiny@intel.com \
--cc=jason.ekstrand@intel.com \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=kenneth.w.graunke@intel.com \
--cc=sanjay.k.kumar@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