From: Christoph Hellwig <hch@lst.de>
To: "Jérôme Glisse" <jglisse@redhat.com>,
"Jason Gunthorpe" <jgg@mellanox.com>,
"Ben Skeggs" <bskeggs@redhat.com>
Cc: Ralph Campbell <rcampbell@nvidia.com>,
Bharata B Rao <bharata@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: turn hmm migrate_vma upside down v2
Date: Thu, 8 Aug 2019 18:33:37 +0300 [thread overview]
Message-ID: <20190808153346.9061-1-hch@lst.de> (raw)
Hi Jérôme, Ben and Jason,
below is a series against the hmm tree which starts revamping the
migrate_vma functionality. The prime idea is to export three slightly
lower level functions and thus avoid the need for migrate_vma_ops
callbacks.
Diffstat:
5 files changed, 281 insertions(+), 607 deletions(-)
A git tree is also available at:
git://git.infradead.org/users/hch/misc.git migrate_vma-cleanup.2
Gitweb:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/migrate_vma-cleanup.2
Changes since v1:
- fix a few whitespace issues
- drop the patch to remove MIGRATE_PFN_WRITE for now
- various spelling fixes
- clear cpages and npages in migrate_vma_setup
- fix the nouveau_dmem_fault_copy_one return value
- minor improvements to some nouveau internal calling conventions
next reply other threads:[~2019-08-08 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 15:33 Christoph Hellwig [this message]
2019-08-08 15:33 ` [PATCH 1/9] mm: turn migrate_vma upside down Christoph Hellwig
2019-08-08 15:33 ` [PATCH 2/9] nouveau: reset dma_nr in nouveau_dmem_migrate_alloc_and_copy Christoph Hellwig
2019-08-08 15:33 ` [PATCH 3/9] nouveau: factor out device memory address calculation Christoph Hellwig
2019-08-08 15:33 ` [PATCH 4/9] nouveau: factor out dmem fence completion Christoph Hellwig
2019-08-08 15:33 ` [PATCH 5/9] nouveau: remove a few function stubs Christoph Hellwig
2019-08-08 15:33 ` [PATCH 6/9] nouveau: simplify nouveau_dmem_migrate_to_ram Christoph Hellwig
2019-08-08 21:10 ` Ralph Campbell
2019-08-10 11:08 ` Christoph Hellwig
2019-08-08 15:33 ` [PATCH 7/9] nouveau: simplify nouveau_dmem_migrate_vma Christoph Hellwig
2019-08-08 15:33 ` [PATCH 8/9] mm: remove the unused MIGRATE_PFN_ERROR flag Christoph Hellwig
2019-08-08 15:33 ` [PATCH 9/9] mm: remove the unused MIGRATE_PFN_DEVICE flag Christoph Hellwig
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=20190808153346.9061-1-hch@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=bharata@linux.ibm.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rcampbell@nvidia.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;
as well as URLs for NNTP newsgroup(s).