From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
Palmer Dabbelt <palmer@sifive.com>,
Stephen Bates <sbates@raithlin.com>,
Logan Gunthorpe <logang@deltatee.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH v2 0/2] Introduce common code for risc-v sparsemem support
Date: Wed, 7 Nov 2018 13:54:31 -0700 [thread overview]
Message-ID: <20181107205433.3875-1-logang@deltatee.com> (raw)
Message-ID: <20181107205431.P3BdVXXx_NtxW-VC1pI2nf2j7BMuIu61ELlc78_IT-I@z> (raw)
These are the first two common patches in my series to introduce
sparsemem support to RISC-V. The full series was posted last cycle
here [1] and the latest version can be found here [2].
As recommended by Palmer, I'd like to get the changes to common code
merged and then I will pursue the cleanups in the individual arches (arm,
arm64, and sh) as well as add the new feature to riscv.
I would suggest we merge these two patches through Andrew's mm tree.
Thanks,
Logan
[1] https://lore.kernel.org/lkml/20181015175702.9036-1-logang@deltatee.com/T/#u
[2] https://github.com/sbates130272/linux-p2pmem.git riscv-sparsemem-v4
--
Changes in v2:
* Added a comment documenting the awkwardly named memblocks_present()
function, as suggested by Andrew.
--
Logan Gunthorpe (2):
mm: Introduce common STRUCT_PAGE_MAX_SHIFT define
mm/sparse: add common helper to mark all memblocks present
arch/arm64/include/asm/memory.h | 9 ---------
arch/arm64/mm/init.c | 8 --------
include/asm-generic/fixmap.h | 1 +
include/linux/mm_types.h | 5 +++++
include/linux/mmzone.h | 6 ++++++
mm/sparse.c | 16 ++++++++++++++++
6 files changed, 28 insertions(+), 17 deletions(-)
--
2.19.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-11-07 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 20:54 Logan Gunthorpe [this message]
2018-11-07 20:54 ` [PATCH v2 0/2] Introduce common code for risc-v sparsemem support Logan Gunthorpe
2018-11-07 20:54 ` [PATCH v2 1/2] mm: Introduce common STRUCT_PAGE_MAX_SHIFT define Logan Gunthorpe
2018-11-07 20:54 ` Logan Gunthorpe
2018-11-08 18:04 ` Catalin Marinas
2018-11-08 18:04 ` Catalin Marinas
2018-11-08 19:13 ` Ard Biesheuvel
2018-11-08 19:13 ` Ard Biesheuvel
2018-11-07 20:54 ` [PATCH v2 2/2] mm/sparse: add common helper to mark all memblocks present Logan Gunthorpe
2018-11-07 20:54 ` Logan Gunthorpe
2018-11-14 18:06 ` [PATCH v2 0/2] Introduce common code for risc-v sparsemem support Palmer Dabbelt
2018-11-14 18:06 ` Palmer Dabbelt
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=20181107205433.3875-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=palmer@sifive.com \
--cc=sbates@raithlin.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).