linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
Cc: "boris.brezillon@collabora.com" <boris.brezillon@collabora.com>,
	"loic.molinari@collabora.com" <loic.molinari@collabora.com>,
	"willy@infradead.org" <willy@infradead.org>,
	"frank.binns@imgtec.com" <frank.binns@imgtec.com>,
	"matt.coster@imgtec.com" <matt.coster@imgtec.com>,
	"maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"mripard@kernel.org" <mripard@kernel.org>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"simona@ffwll.ch" <simona@ffwll.ch>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: RE: [PATCH v4 5/6] drm/gem-shmem: Track folio accessed/dirty status in mmap
Date: Fri, 13 Mar 2026 10:03:53 +0000	[thread overview]
Message-ID: <TY3PR01MB11346D3DCB34CEF0C71086DD48645A@TY3PR01MB11346.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20a82a3c-80ed-4f9a-912b-088284c27b68@suse.de>

Hi Thomas,

> -----Original Message-----
> From: Thomas Zimmermann <tzimmermann@suse.de>
> Sent: 13 March 2026 08:01
> Subject: Re: [PATCH v4 5/6] drm/gem-shmem: Track folio accessed/dirty status in mmap
> 
> >   const struct vm_operations_struct drm_gem_shmem_vm_ops = {
> >   	.fault = drm_gem_shmem_fault,
> >   	.open = drm_gem_shmem_vm_open,
> >   	.close = drm_gem_shmem_vm_close,
> > +	.pfn_mkwrite = drm_gem_shmem_pfn_mkwrite,

Commenting this makes weston to work. Kmscube works without this change.

Cheers,
Biju

  parent reply	other threads:[~2026-03-13 10:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 11:42 [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status Thomas Zimmermann
2026-02-27 11:42 ` [PATCH v4 1/6] drm/gem-shmem: Use obj directly where appropriate in fault handler Thomas Zimmermann
2026-02-27 11:42 ` [PATCH v4 2/6] drm/gem-shmem: Test for existence of page in mmap " Thomas Zimmermann
2026-02-27 11:42 ` [PATCH v4 3/6] drm/gem-shmem: Return vm_fault_t from drm_gem_shmem_try_map_pmd() Thomas Zimmermann
2026-02-27 11:42 ` [PATCH v4 4/6] drm/gem-shmem: Refactor drm_gem_shmem_try_map_pmd() Thomas Zimmermann
2026-02-27 11:42 ` [PATCH v4 5/6] drm/gem-shmem: Track folio accessed/dirty status in mmap Thomas Zimmermann
2026-03-12 17:36   ` Tommaso Merciai
2026-03-12 17:46     ` Biju Das
2026-03-13  6:44       ` Biju Das
2026-03-13  8:00         ` Thomas Zimmermann
2026-03-13  8:41           ` Biju Das
2026-03-13 10:03           ` Biju Das [this message]
2026-03-13 10:18         ` Boris Brezillon
2026-03-13 10:29           ` Thomas Zimmermann
2026-03-13 10:33             ` Biju Das
2026-03-13 10:52             ` Boris Brezillon
2026-03-13 11:56             ` Boris Brezillon
2026-03-13 12:04               ` Biju Das
2026-03-13 12:18                 ` Boris Brezillon
2026-03-13 12:43                   ` Boris Brezillon
2026-03-13 12:55                     ` Boris Brezillon
2026-03-13 17:45                       ` Boris Brezillon
2026-03-14  9:42                         ` Biju Das
2026-03-19 14:17                           ` Biju Das
2026-03-19 14:50                             ` Boris Brezillon
2026-03-19 14:53                               ` Biju Das
2026-03-16  8:45                         ` Thomas Zimmermann
2026-03-16  9:36                           ` Boris Brezillon
2026-03-16 10:22                             ` Thomas Zimmermann
2026-03-16 10:53                               ` Boris Brezillon
2026-03-16 15:30                           ` Boris Brezillon
2026-03-13  8:33       ` Thomas Zimmermann
2026-03-13  8:47         ` Biju Das
2026-03-13  9:24         ` Tommaso Merciai
2026-02-27 11:42 ` [PATCH v4 6/6] drm/gem-shmem: Track folio accessed/dirty status in vmap Thomas Zimmermann

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=TY3PR01MB11346D3DCB34CEF0C71086DD48645A@TY3PR01MB11346.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frank.binns@imgtec.com \
    --cc=linux-mm@kvack.org \
    --cc=loic.molinari@collabora.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt.coster@imgtec.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tommaso.merciai.xr@bp.renesas.com \
    --cc=tzimmermann@suse.de \
    --cc=willy@infradead.org \
    /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