From: Andrew Morton <akpm@linux-foundation.org>
To: jglisse@redhat.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Subhash Gutti <sgutti@nvidia.com>,
Evgeny Baskakov <ebaskakov@nvidia.com>
Subject: Re: [PATCH] mm/hmm: struct hmm is only use by HMM mirror functionality
Date: Fri, 25 Aug 2017 13:01:46 -0700 [thread overview]
Message-ID: <20170825130146.81f28f23a06a22b55270074a@linux-foundation.org> (raw)
In-Reply-To: <1503621746-17876-1-git-send-email-jglisse@redhat.com>
On Thu, 24 Aug 2017 20:42:26 -0400 jglisse@redhat.com wrote:
> The struct hmm is only use if the HMM mirror functionality is enabled
> move associated code behind CONFIG_HMM_MIRROR to avoid build error if
> one enable some of the HMM memory configuration without the mirror
> feature.
It's unclear whether this patch is in addition to Arnd's "mm: HMM always
needs MMU_NOTIFIER" or is a replacement for it. (If the latter, it
should have Arnd's Reported-by). But I cannot get this patch to apply
cleanly in either situation.
So I'll skip both patches. Please send something which applies on top
of
hmm-heterogeneous-memory-management-documentation-v3.patch
mm-hmm-heterogeneous-memory-management-hmm-for-short-v5.patch
mm-hmm-mirror-mirror-process-address-space-on-device-with-hmm-helpers-v3.patch
mm-hmm-mirror-helper-to-snapshot-cpu-page-table-v4.patch
mm-hmm-mirror-device-page-fault-handler.patch
mm-memory_hotplug-introduce-add_pages.patch
mm-zone_device-new-type-of-zone_device-for-unaddressable-memory-v5.patch
mm-zone_device-new-type-of-zone_device-for-unaddressable-memory-fix.patch
mm-zone_device-special-case-put_page-for-device-private-pages-v4.patch
mm-memcontrol-allow-to-uncharge-page-without-using-page-lru-field.patch
mm-memcontrol-support-memory_device_private-v4.patch
mm-hmm-devmem-device-memory-hotplug-using-zone_device-v7.patch
mm-hmm-devmem-dummy-hmm-device-for-zone_device-memory-v3.patch
mm-migrate-new-migrate-mode-migrate_sync_no_copy.patch
mm-migrate-new-memory-migration-helper-for-use-with-device-memory-v5.patch
mm-migrate-migrate_vma-unmap-page-from-vma-while-collecting-pages.patch
mm-migrate-support-un-addressable-zone_device-page-in-migration-v3.patch
mm-migrate-allow-migrate_vma-to-alloc-new-page-on-empty-entry-v4.patch
mm-device-public-memory-device-memory-cache-coherent-with-cpu-v5.patch
mm-hmm-add-new-helper-to-hotplug-cdm-memory-region-v3.patch
#
mm-hmm-avoid-bloating-arch-that-do-not-make-use-of-hmm.patch
thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-08-25 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 23:08 [PATCH] mm: HMM always needs MMU_NOTIFIER Arnd Bergmann
2017-08-25 0:42 ` [PATCH] mm/hmm: struct hmm is only use by HMM mirror functionality jglisse
2017-08-25 20:01 ` Andrew Morton [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=20170825130146.81f28f23a06a22b55270074a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebaskakov@nvidia.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.au \
--cc=sgutti@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).