From: Jason Gunthorpe <jgg@ziepe.ca>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org
Subject: Re: [PATCH v2 0/7] mm/hmm: more HMM clean up
Date: Fri, 26 Jul 2019 12:45:32 -0300 [thread overview]
Message-ID: <20190726154532.GA29678@ziepe.ca> (raw)
In-Reply-To: <20190726005650.2566-1-rcampbell@nvidia.com>
On Thu, Jul 25, 2019 at 05:56:43PM -0700, Ralph Campbell wrote:
> Here are seven more patches for things I found to clean up.
> This was based on top of Christoph's seven patches:
> "hmm_range_fault related fixes and legacy API removal v3".
> I assume this will go into Jason's tree since there will likely be
> more HMM changes in this cycle.
>
> Changes from v1 to v2:
>
> Added AMD GPU to hmm_update removal.
> Added 2 patches from Christoph.
> Added 2 patches as a result of Jason's suggestions.
>
> Christoph Hellwig (2):
> mm/hmm: replace the block argument to hmm_range_fault with a flags
> value
> mm: merge hmm_range_snapshot into hmm_range_fault
>
> Ralph Campbell (5):
> mm/hmm: replace hmm_update with mmu_notifier_range
> mm/hmm: a few more C style and comment clean ups
> mm/hmm: remove hugetlbfs check in hmm_vma_walk_pmd
> mm/hmm: remove hmm_range vma
For all of these:
Reviewed-by: Jason Gunthorpe <jgg@mellanox.com>
I've applied this to hmm.git, excluding:
> mm/hmm: make full use of walk_page_range()
Pending further discussion.
Based on last cycle I've decided to move good patches into linux-next
earlier and rely on some rebase if needed. This is to help Andrew's
workflow.
So, if there are more tags/etc please continue to send them, I will
sort it..
Thanks,
Jason
prev parent reply other threads:[~2019-07-26 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 0:56 [PATCH v2 0/7] mm/hmm: more HMM clean up Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
[not found] ` <20190726005650.2566-1-rcampbell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2019-07-26 0:56 ` [PATCH v2 1/7] mm/hmm: replace hmm_update with mmu_notifier_range Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 0:56 ` [PATCH v2 4/7] mm: merge hmm_range_snapshot into hmm_range_fault Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 0:56 ` [PATCH v2 5/7] mm/hmm: make full use of walk_page_range() Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
[not found] ` <20190726005650.2566-6-rcampbell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2019-07-26 6:24 ` Christoph Hellwig
2019-07-26 6:24 ` Christoph Hellwig
2019-07-26 15:12 ` Jason Gunthorpe
2019-07-26 15:12 ` Jason Gunthorpe
2019-07-26 0:56 ` [PATCH v2 7/7] mm/hmm: remove hmm_range vma Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 6:25 ` Christoph Hellwig
2019-07-26 0:56 ` [PATCH v2 2/7] mm/hmm: a few more C style and comment clean ups Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 6:23 ` Christoph Hellwig
2019-07-26 17:11 ` Ralph Campbell
2019-07-26 0:56 ` [PATCH v2 3/7] mm/hmm: replace the block argument to hmm_range_fault with a flags value Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 0:56 ` [PATCH v2 6/7] mm/hmm: remove hugetlbfs check in hmm_vma_walk_pmd Ralph Campbell
2019-07-26 0:56 ` Ralph Campbell
2019-07-26 6:24 ` Christoph Hellwig
2019-07-26 15:45 ` Jason Gunthorpe [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=20190726154532.GA29678@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--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 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.