linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Loïc Molinari" <loic.molinari@collabora.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Rob Herring" <robh@kernel.org>,
	"Steven Price" <steven.price@arm.com>,
	"Liviu Dudau" <liviu.dudau@arm.com>,
	"Melissa Wen" <mwen@igalia.com>,
	"Maíra Canal" <mcanal@igalia.com>,
	"Hugh Dickins" <hughd@google.com>,
	"Baolin Wang" <baolin.wang@linux.alibaba.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	"Mikołaj Wasiak" <mikolaj.wasiak@intel.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Nitin Gote" <nitin.r.gote@intel.com>,
	"Andi Shyti" <andi.shyti@linux.intel.com>,
	"Christopher Healy" <healych@amazon.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-mm@kvack.org,
	kernel@collabora.com
Subject: Re: [PATCH v3 10/10] Documentation/gpu/drm-mm: Add THP paragraph to GEM mapping section
Date: Sun, 5 Oct 2025 05:40:19 +0700	[thread overview]
Message-ID: <aOGiU77k1XPb9W9M@archie.me> (raw)
In-Reply-To: <20251004093054.21388-11-loic.molinari@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

On Sat, Oct 04, 2025 at 11:30:53AM +0200, Loïc Molinari wrote:
> @@ -290,7 +292,7 @@ The open and close operations must update the GEM object reference
>  count. Drivers can use the drm_gem_vm_open() and drm_gem_vm_close() helper
>  functions directly as open and close handlers.
>  
> -The fault operation handler is responsible for mapping individual pages
> +The fault operation handlers are responsible for mapping individual pages
>  to userspace when a page fault occurs. Depending on the memory
>  allocation scheme, drivers can allocate pages at fault time, or can
>  decide to allocate memory for the GEM object at the time the object is
> @@ -299,6 +301,19 @@ created.
>  Drivers that want to map the GEM object upfront instead of handling page
>  faults can implement their own mmap file operation handler.
>  
> +In order to reduce page table overhead, if the internal shmem mountpoint
> +"shm_mnt" is configured to use transparent huge pages (for builds with
> +CONFIG_TRANSPARENT_HUGEPAGE enabled) and if the shmem backing store
> +manages to allocate huge pages, faulty addresses within huge pages will
> +be mapped into the tables using the huge page fault handler. In such
> +cases, mmap() user address alignment for GEM objects is handled by
> +providing a custom get_unmapped_area properly forwarding to the shmem
> +backing store. For most drivers, which don't create a huge mountpoint by
> +default or through a module parameter, transparent huge pages can be
> +enabled by either setting the "transparent_hugepage_shmem" kernel
> +parameter or the "/sys/kernel/mm/transparent_hugepage/shmem_enabled"
> +sysfs knob.
> +
>  For platforms without MMU the GEM core provides a helper method
>  drm_gem_dma_get_unmapped_area(). The mmap() routines will call this to get a
>  proposed address for the mapping.
 
LGTM, thanks!

Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-10-04 22:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-04  9:30 [PATCH v3 00/10] drm: Reduce page tables overhead with THP Loïc Molinari
2025-10-04  9:30 ` [PATCH v3 01/10] drm/shmem-helper: Add huge page fault handler Loïc Molinari
2025-10-04 22:53   ` Matthew Wilcox
2025-10-06  6:52   ` Boris Brezillon
2025-10-06 16:01   ` Andi Shyti
2025-10-04  9:30 ` [PATCH v3 02/10] drm/gem: Introduce drm_gem_get_unmapped_area() fop Loïc Molinari
2025-10-10  7:48   ` kernel test robot
2025-10-04  9:30 ` [PATCH v3 03/10] drm/gem: Add huge tmpfs mount point helper Loïc Molinari
2025-10-04 20:34   ` Al Viro
2025-10-06  6:58   ` Boris Brezillon
2025-10-06  7:02   ` Boris Brezillon
2025-10-04  9:30 ` [PATCH v3 04/10] drm/i915: Use " Loïc Molinari
2025-10-04  9:30 ` [PATCH v3 05/10] drm/v3d: " Loïc Molinari
2025-10-06  7:07   ` Boris Brezillon
2025-10-04  9:30 ` [PATCH v3 06/10] drm/gem: Get rid of *_with_mnt helpers Loïc Molinari
2025-10-06  7:17   ` Boris Brezillon
2025-10-04  9:30 ` [PATCH v3 07/10] drm/panthor: Introduce huge tmpfs mount point option Loïc Molinari
2025-10-06  7:28   ` Boris Brezillon
2025-10-15 13:09     ` Loïc Molinari
2025-10-15 13:12       ` Boris Brezillon
2025-10-06  7:34   ` Boris Brezillon
2025-10-04  9:30 ` [PATCH v3 08/10] drm/panthor: Improve IOMMU map/unmap debugging logs Loïc Molinari
2025-10-04  9:30 ` [PATCH v3 09/10] drm/panfrost: Introduce huge tmpfs mount point option Loïc Molinari
2025-10-06  7:33   ` Boris Brezillon
2025-10-04  9:30 ` [PATCH v3 10/10] Documentation/gpu/drm-mm: Add THP paragraph to GEM mapping section Loïc Molinari
2025-10-04 22:40   ` Bagas Sanjaya [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=aOGiU77k1XPb9W9M@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi.shyti@linux.intel.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=boris.brezillon@collabora.com \
    --cc=brauner@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=healych@amazon.com \
    --cc=hughd@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liviu.dudau@arm.com \
    --cc=loic.molinari@collabora.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mcanal@igalia.com \
    --cc=mikolaj.wasiak@intel.com \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --cc=nitin.r.gote@intel.com \
    --cc=robh@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=steven.price@arm.com \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    /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