All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
To: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"Kirill A . Shutemov" <kirill@shutemov.name>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Will Deacon" <will.deacon@arm.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Rik van Riel" <riel@surriel.com>,
	"Minchan Kim" <minchan@kernel.org>,
	"Michal Hocko" <mhocko@suse.com>,
	"Huang Ying" <ying.huang@intel.com>,
	"Jérôme Glisse" <jglisse@redhat.com>
Subject: -mm maintainer? WAS Re: [PATCH v6 0/8] Emulated coherent graphics memory take 2
Date: Mon, 4 Nov 2019 10:21:26 +0100	[thread overview]
Message-ID: <a31f0d40-d8a5-faca-016b-0066f5ac31a2@shipmail.org> (raw)
In-Reply-To: <20191014132204.7721-1-thomas_os@shipmail.org>

Hi, All,

On 10/14/19 3:22 PM, Thomas Hellström (VMware) wrote:
> From: Thomas Hellström <thellstrom@vmware.com>
>
> Graphics APIs like OpenGL 4.4 and Vulkan require the graphics driver
> to provide coherent graphics memory, meaning that the GPU sees any
> content written to the coherent memory on the next GPU operation that
> touches that memory, and the CPU sees any content written by the GPU
> to that memory immediately after any fence object trailing the GPU
> operation is signaled.
>
> Paravirtual drivers that otherwise require explicit synchronization
> needs to do this by hooking up dirty tracking to pagefault handlers
> and buffer object validation.
>
> Provide mm helpers needed for this and that also allow for huge pmd-
> and pud entries (patch 1-3), and the associated vmwgfx code (patch 4-7).
>
> The code has been tested and exercised by a tailored version of mesa
> where we disable all explicit synchronization and assume graphics memory
> is coherent. The performance loss varies of course; a typical number is
> around 5%.
>
> I would like to merge this code through the DRM tree, so an ack to include
> the new mm helpers in that merge would be greatly appreciated.
>

I'm a bit confused as how to get this merged? Is there an -mm maintainer 
or who is supposed to ack -mm patches and get them into the kernel?

Any input appreciated,

Thanks,

Thomas



  parent reply	other threads:[~2019-11-04  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 13:21 [PATCH v6 0/8] Emulated coherent graphics memory take 2 Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 1/8] mm: Remove BUG_ON mmap_sem not held from xxx_trans_huge_lock() Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 2/8] mm: pagewalk: Take the pagetable lock in walk_pte_range() Thomas Hellström (VMware)
2019-10-14 13:21 ` [PATCH v6 3/8] mm: Add a walk_page_mapping() function to the pagewalk code Thomas Hellström (VMware)
2019-11-06  3:49   ` Andrew Morton
2019-10-14 13:22 ` [PATCH v6 4/8] mm: Add write-protect and clean utilities for address space ranges Thomas Hellström (VMware)
2019-11-06  3:51   ` Andrew Morton
2019-10-14 13:22 ` [PATCH v6 5/8] drm/vmwgfx: Implement an infrastructure for write-coherent resources Thomas Hellström (VMware)
2019-10-14 16:19   ` kbuild test robot
2019-10-14 13:22 ` [PATCH v6 6/8] drm/vmwgfx: Use an RBtree instead of linked list for MOB resources Thomas Hellström (VMware)
2019-10-14 13:22 ` [PATCH v6 7/8] drm/vmwgfx: Implement an infrastructure for read-coherent resources Thomas Hellström (VMware)
2019-10-14 13:22 ` [PATCH v6 8/8] drm/vmwgfx: Add surface dirty-tracking callbacks Thomas Hellström (VMware)
2019-10-21 12:24 ` [PATCH v6 0/8] Emulated coherent graphics memory take 2 Thomas Hellstrom
2019-11-04  9:21 ` Thomas Hellström (VMware) [this message]
2019-11-04 16:36   ` -mm maintainer? WAS " Linus Torvalds

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=a31f0d40-d8a5-faca-016b-0066f5ac31a2@shipmail.org \
    --to=thomas_os@shipmail.org \
    --cc=akpm@linux-foundation.org \
    --cc=jglisse@redhat.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@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.