From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: npiggin@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, David Gibson <david@gibson.dropbear.id.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [RFC PATCH 0/3] Add support for compound page migration in mm_iommu_get
Date: Mon, 3 Sep 2018 22:07:30 +0530 [thread overview]
Message-ID: <20180903163733.27965-1-aneesh.kumar@linux.ibm.com> (raw)
This patch series add support for migrating compound pages if we find them in the
CMA area before taking long term page reference for VFIO.
Testing:
* TODO: test with hugetlb backed guest ram.
* Testing done with a code change as below
- if (is_migrate_cma_page(pages[i]) && migrate_allow) {
+ if (migrate_allow) {
...
+ migrate_allow = false;
Aneesh Kumar K.V (3):
mm: Export alloc_migrate_huge_page
powerpc/mm/iommu: Allow large IOMMU page size only for hugetlb backing
powerpc/mm/iommu: Allow migration of cma allocated pages during
mm_iommu_get
arch/powerpc/mm/mmu_context_iommu.c | 209 +++++++++++++++++-----------
include/linux/hugetlb.h | 2 +
mm/hugetlb.c | 4 +-
3 files changed, 128 insertions(+), 87 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-03 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 16:37 Aneesh Kumar K.V [this message]
2018-09-03 16:37 ` [RFC PATCH 1/3] mm: Export alloc_migrate_huge_page Aneesh Kumar K.V
2018-09-04 3:57 ` David Gibson
2018-09-03 16:37 ` [RFC PATCH 2/3] powerpc/mm/iommu: Allow large IOMMU page size only for hugetlb backing Aneesh Kumar K.V
2018-09-04 4:06 ` David Gibson
2018-09-04 8:42 ` Aneesh Kumar K.V
2018-09-03 16:37 ` [RFC PATCH 3/3] powerpc/mm/iommu: Allow migration of cma allocated pages during mm_iommu_get Aneesh Kumar K.V
2018-09-18 3:51 ` David Gibson
2018-09-18 13:53 ` Aneesh Kumar K.V
2018-09-04 2:36 ` [RFC PATCH 0/3] Add support for compound page migration in mm_iommu_get Aneesh Kumar K.V
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=20180903163733.27965-1-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
/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.