From: Christoph Hellwig <hch@infradead.org>
To: "Thomas Hellström (VMware)" <thellstrom@vmwopensource.org>
Cc: dri-devel@lists.freedesktop.org,
linux-graphics-maintainer@vmware.com, pv-drivers@vmware.com,
linux-kernel@vger.kernel.org, nadav.amit@gmail.com,
"Thomas Hellstrom" <thellstrom@vmware.com>,
"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>,
"Souptick Joarder" <jrdr.linux@gmail.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
linux-mm@kvack.org, "Ralph Campbell" <rcampbell@nvidia.com>
Subject: Re: [PATCH v5 3/9] mm: Add write-protect and clean utilities for address space ranges
Date: Wed, 12 Jun 2019 04:23:50 -0700 [thread overview]
Message-ID: <20190612112349.GA20226@infradead.org> (raw)
In-Reply-To: <20190612064243.55340-4-thellstrom@vmwopensource.org>
On Wed, Jun 12, 2019 at 08:42:37AM +0200, Thomas Hellström (VMware) wrote:
> From: Thomas Hellstrom <thellstrom@vmware.com>
>
> Add two utilities to a) write-protect and b) clean all ptes pointing into
> a range of an address space.
> The utilities are intended to aid in tracking dirty pages (either
> driver-allocated system memory or pci device memory).
> The write-protect utility should be used in conjunction with
> page_mkwrite() and pfn_mkwrite() to trigger write page-faults on page
> accesses. Typically one would want to use this on sparse accesses into
> large memory regions. The clean utility should be used to utilize
> hardware dirtying functionality and avoid the overhead of page-faults,
> typically on large accesses into small memory regions.
Please use EXPORT_SYMBOL_GPL, just like for apply_to_page_range and
friends. Also in general new core functionality like this should go
along with the actual user, we don't need to repeat the hmm disaster.
next prev parent reply other threads:[~2019-06-12 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 6:42 [PATCH v5 0/9] Emulated coherent graphics memory Thomas Hellström (VMware)
2019-06-12 6:42 ` [PATCH v5 1/9] mm: Allow the [page|pfn]_mkwrite callbacks to drop the mmap_sem Thomas Hellström (VMware)
2019-06-12 6:42 ` [PATCH v5 2/9] mm: Add an apply_to_pfn_range interface Thomas Hellström (VMware)
2019-06-12 12:16 ` Christoph Hellwig
2019-06-12 12:26 ` Thomas Hellström (VMware)
2019-06-12 6:42 ` [PATCH v5 3/9] mm: Add write-protect and clean utilities for address space ranges Thomas Hellström (VMware)
2019-06-12 11:23 ` Christoph Hellwig [this message]
2019-06-12 12:13 ` Christoph Hellwig
2019-06-12 12:20 ` Thomas Hellström (VMware)
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=20190612112349.GA20226@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.com \
--cc=rcampbell@nvidia.com \
--cc=riel@surriel.com \
--cc=thellstrom@vmware.com \
--cc=thellstrom@vmwopensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox