From: Jason Gunthorpe <jgg@ziepe.ca>
To: Christoph Hellwig <hch@lst.de>
Cc: Jerome Glisse <jglisse@redhat.com>,
Ralph Campbell <rcampbell@nvidia.com>,
linux-mm@kvack.org
Subject: Re: misc hmm cleanups
Date: Wed, 18 Mar 2020 21:27:38 -0300 [thread overview]
Message-ID: <20200319002738.GF20941@ziepe.ca> (raw)
In-Reply-To: <20200317185537.GA20962@lst.de>
On Tue, Mar 17, 2020 at 07:55:37PM +0100, Christoph Hellwig wrote:
> On Tue, Mar 17, 2020 at 03:38:23PM -0300, Jason Gunthorpe wrote:
> > On Mon, Mar 16, 2020 at 02:53:05PM +0100, Christoph Hellwig wrote:
> > > Hi Jason,
> > >
> > > I started looking at bits in my backlog that shouldn't get too much
> > > in your way. Here is a bunch of simple patches, on top of the series
> > > you sent out.
> >
> > I applied these two, I made the edits discussed to the last two
> > patches, and ran the series over the hmm tester Ralph has.
> >
> > Please take a quick check:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=hmm&id=2a60cfb32b260468dc81dfc1f56fc0f9ebe9f2e5
> > https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=hmm&id=ee37d9e6e47439fbd3a72b7c6a13b8ce216fb125
> >
> > - Edited commit message to point out that the NONE set is a bug and
> > add fixes line.
> > - Drop the pfn error and update the commit message, remove now unused
> > pfn and i vars
>
> I wonder if just having those fixes as separate commits would have
> been more clear. But the updated patches do look correct to me.
Ok, I agree the last one removing the pfns is a bit of overreach, even
if the -EPERM exit looks bad when it is de-inlined. I will sort it in
a following patch
I like the NONE one though
So, I swapped the last back to your original
I hope to rebase some of my remaining series tomorrow. Things are
crazy here right now.
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=hmm&id=ede58c05bec9e5ccf659cf001bb969963806bed0
Thanks,
Jason
prev parent reply other threads:[~2020-03-19 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 13:53 misc hmm cleanups Christoph Hellwig
2020-03-16 13:53 ` [PATCH 1/5] mm: don't provide a stub for hmm_range_fault Christoph Hellwig
2020-03-16 14:37 ` Zi Yan
2020-03-16 16:45 ` Jason Gunthorpe
2020-03-16 13:53 ` [PATCH 2/5] mm: remove the unused HMM_FAULT_ALLOW_RETRY flag Christoph Hellwig
2020-03-16 16:44 ` Jason Gunthorpe
2020-03-16 13:53 ` [PATCH 3/5] mm: simplify hmm_vma_walk_hugetlb_entry Christoph Hellwig
2020-03-16 16:43 ` Jason Gunthorpe
2020-03-16 13:53 ` [PATCH 4/5] mm: don't handle the non-fault case in hmm_vma_walk_hole_ Christoph Hellwig
2020-03-16 16:43 ` Jason Gunthorpe
2020-03-16 13:53 ` [PATCH 5/5] mm: merge hmm_vma_do_fault into into hmm_vma_walk_hole_ Christoph Hellwig
2020-03-16 16:41 ` Jason Gunthorpe
2020-03-16 16:51 ` Christoph Hellwig
2020-03-16 18:01 ` Christoph Hellwig
2020-03-17 18:38 ` misc hmm cleanups Jason Gunthorpe
2020-03-17 18:55 ` Christoph Hellwig
2020-03-19 0:27 ` 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=20200319002738.GF20941@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=hch@lst.de \
--cc=jglisse@redhat.com \
--cc=linux-mm@kvack.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.