From: Nicolas Boichat <drinkcat@chromium.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Will Deacon <will.deacon@arm.com>, Joerg Roedel <joro@8bytes.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
Mel Gorman <mgorman@techsingularity.net>,
Levin Alexander <alexander.levin@verizon.com>,
Huaisheng Ye <yehs1@lenovo.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Yong Wu <yong.wu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tomasz Figa <tfiga@google.com>,
yingjoe.chen@mediatek.com
Subject: [PATCH RFC 0/3] iommu/io-pgtable-arm-v7s: Use DMA32 zone for page tables
Date: Fri, 9 Nov 2018 16:24:45 +0800 [thread overview]
Message-ID: <20181109082448.150302-1-drinkcat@chromium.org> (raw)
This is a follow-up to the discussion in [1], to make sure that the page tables
allocated by iommu/io-pgtable-arm-v7s are contained within 32-bit physical
address space.
[1] https://lists.linuxfoundation.org/pipermail/iommu/2018-November/030876.html
Nicolas Boichat (3):
mm: When CONFIG_ZONE_DMA32 is set, use DMA32 for SLAB_CACHE_DMA
include/linux/gfp.h: Add __get_dma32_pages macro
iommu/io-pgtable-arm-v7s: Request DMA32 memory, and improve debugging
drivers/iommu/io-pgtable-arm-v7s.c | 6 ++++--
include/linux/gfp.h | 2 ++
include/linux/slab.h | 13 ++++++++++++-
mm/slab.c | 2 +-
mm/slub.c | 2 +-
5 files changed, 20 insertions(+), 5 deletions(-)
--
2.19.1.930.g4563a0d9d0-goog
WARNING: multiple messages have this Message-ID (diff)
From: drinkcat@chromium.org (Nicolas Boichat)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/3] iommu/io-pgtable-arm-v7s: Use DMA32 zone for page tables
Date: Fri, 9 Nov 2018 16:24:45 +0800 [thread overview]
Message-ID: <20181109082448.150302-1-drinkcat@chromium.org> (raw)
This is a follow-up to the discussion in [1], to make sure that the page tables
allocated by iommu/io-pgtable-arm-v7s are contained within 32-bit physical
address space.
[1] https://lists.linuxfoundation.org/pipermail/iommu/2018-November/030876.html
Nicolas Boichat (3):
mm: When CONFIG_ZONE_DMA32 is set, use DMA32 for SLAB_CACHE_DMA
include/linux/gfp.h: Add __get_dma32_pages macro
iommu/io-pgtable-arm-v7s: Request DMA32 memory, and improve debugging
drivers/iommu/io-pgtable-arm-v7s.c | 6 ++++--
include/linux/gfp.h | 2 ++
include/linux/slab.h | 13 ++++++++++++-
mm/slab.c | 2 +-
mm/slub.c | 2 +-
5 files changed, 20 insertions(+), 5 deletions(-)
--
2.19.1.930.g4563a0d9d0-goog
next reply other threads:[~2018-11-09 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 8:24 Nicolas Boichat [this message]
2018-11-09 8:24 ` [PATCH RFC 0/3] iommu/io-pgtable-arm-v7s: Use DMA32 zone for page tables Nicolas Boichat
2018-11-09 8:24 ` [PATCH RFC 1/3] mm: When CONFIG_ZONE_DMA32 is set, use DMA32 for SLAB_CACHE_DMA Nicolas Boichat
2018-11-09 8:24 ` Nicolas Boichat
2018-11-09 10:43 ` Vlastimil Babka
2018-11-09 10:43 ` Vlastimil Babka
2018-11-09 11:57 ` Nicolas Boichat
2018-11-09 11:57 ` Nicolas Boichat
2018-11-09 12:14 ` Vlastimil Babka
2018-11-09 12:14 ` Vlastimil Babka
2018-11-09 8:24 ` [PATCH RFC 2/3] include/linux/gfp.h: Add __get_dma32_pages macro Nicolas Boichat
2018-11-09 8:24 ` Nicolas Boichat
2018-11-09 8:24 ` [PATCH RFC 3/3] iommu/io-pgtable-arm-v7s: Request DMA32 memory, and improve debugging Nicolas Boichat
2018-11-09 8:24 ` Nicolas Boichat
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=20181109082448.150302-1-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=tfiga@google.com \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=yehs1@lenovo.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yong.wu@mediatek.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.