linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: David Hildenbrand <david@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@lst.de>, Hugh Dickins <hughd@google.com>,
	Alex Sierra <alex.sierra@amd.com>,
	Alistair Popple <apopple@nvidia.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Mike Rapoport <rppt@kernel.org>,
	William Kucharski <william.kucharski@oracle.com>
Subject: Re: [GIT PULL] Folio patches for 5.18 (MM part)
Date: Mon, 21 Mar 2022 16:54:12 +0000	[thread overview]
Message-ID: <YjittBLCYpft5ALc@casper.infradead.org> (raw)
In-Reply-To: <9ece8da5-ae0c-fe1c-ff2f-961f641c00fe@redhat.com>

On Mon, Mar 21, 2022 at 04:38:22PM +0100, David Hildenbrand wrote:
> On 21.03.22 16:31, Matthew Wilcox wrote:
> >>>> Alex Sierra (10):
> >>>>       mm: add zone device coherent type memory support
> >>>>       mm: add device coherent vma selection for memory migration
> >>>>       mm/gup: fail get_user_pages for LONGTERM dev coherent type
> >>>>       drm/amdkfd: add SPM support for SVM
> >>>>       drm/amdkfd: coherent type as sys mem on migration to ram
> >>>>       lib: test_hmm add ioctl to get zone device type
> >>>>       lib: test_hmm add module param for zone device type
> >>>>       lib: add support for device coherent type in test_hmm
> >>>>       tools: update hmm-test to support device coherent type
> >>>>       tools: update test_hmm script to support SP config
> >>>>
> >>>> Alistair Popple (2):
> >>>>       mm: remove the vma check in migrate_vma_setup()
> >>>>       mm/gup: migrate device coherent pages when pinning instead of failing
> >>>
> >>> ... I thought DEVICE_COHERENT is still under development?
> >>>
> >>
> >> After verifying that I'm not daydreaming [1] (and realizing that I had
> >> review comments to some of these patches that have not been resolved
> >> yet) and also not spotting these change in your changelog above, I
> >> assume this stuff was included by mistake. NACK to merging
> >> DEVICE_COHERENT at this point.
> >>
> >> [1] https://lkml.kernel.org/r/20220310172633.9151-1-alex.sierra@amd.com
> > 
> > That patch ("split vm_normal_pages for LRU and non-LRU handling") isn't
> > included in this pull request.  The patches I have were those sent by
> > Christoph here:
> > 
> > https://lore.kernel.org/linux-mm/20220210072828.2930359-1-hch@lst.de/
> > 
> > I can drop any patches that you have objections to, but I don't see
> > any objections from you to any patches in that list.
> 
> Well, I was discussing with the original authors about how to proceed.
> 
> Quoting from:
> 
> https://lkml.kernel.org/r/1747447c-202d-9195-9d44-57f299be48c4@amd.com
> 
> "
> Yes, it should be part of that series. Alex developed it on top of the
> series for now. But I think eventually it would need to be spliced into it.

It wasn't clear to me that you were talking about this series.

> Patch1 would need to go somewhere before the other DEVICE_COHERENT
> patches (with minor modifications). Patch 2 could be squashed into
> "tools: add hmm gup test for long term pinned device pages" or go next
> to it. Patch 3 doesn't have a direct dependency on device-coherent
> pages. It only mentions them in comments.
> "
> 
> I can understand that Christoph included a rebased version in his rework
> (to keep it working in -next and/or help the original authors?), but to
> me that doesn't mean that the feature is finally done.

OK, so you object to the last 12 patches from Alistair and Alex?  And
you're OK with the preceeding 15 patches from Christoph?  I can put
together a pull request for that combination.



  reply	other threads:[~2022-03-21 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 13:30 Matthew Wilcox
2022-03-21 15:16 ` David Hildenbrand
2022-03-21 15:24   ` David Hildenbrand
2022-03-21 15:31     ` Matthew Wilcox
2022-03-21 15:38       ` David Hildenbrand
2022-03-21 16:54         ` Matthew Wilcox [this message]
2022-03-21 17:03           ` David Hildenbrand
2022-03-21 17:49             ` Matthew Wilcox
2022-03-23  2:27               ` pr-tracker-bot

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=YjittBLCYpft5ALc@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.sierra@amd.com \
    --cc=apopple@nvidia.com \
    --cc=david@redhat.com \
    --cc=hch@lst.de \
    --cc=hughd@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=william.kucharski@oracle.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