From: Logan Gunthorpe <logang@deltatee.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Rob Herring <robh@kernel.org>, Albert Ou <aou@eecs.berkeley.edu>,
Andrew Waterman <andrew@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org,
Michael Clark <michaeljclark@mac.com>,
Zong Li <zong@andestech.com>, Olof Johansson <olof@lixom.net>,
Greentime Hu <greentime.hu@sifive.com>,
linux-riscv@lists.infradead.org,
Stephen Bates <sbates@raithlin.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v6] RISC-V: Implement sparsemem
Date: Thu, 29 Aug 2019 09:46:37 -0600 [thread overview]
Message-ID: <80a6c33f-6914-ee5f-7456-e1bf3d8801e0@deltatee.com> (raw)
In-Reply-To: <20190829062123.GA16471@rapoport-lnx>
On 2019-08-29 12:21 a.m., Mike Rapoport wrote:
> On Wed, Aug 28, 2019 at 03:40:54PM -0600, Logan Gunthorpe wrote:
>> Implement sparsemem support for Risc-v which helps pave the
>> way for memory hotplug and eventually P2P support.
>>
>> Introduce Kconfig options for virtual and physical address bits which
>> are used to calculate the size of the vmemmap and set the
>> MAX_PHYSMEM_BITS.
>>
>> The vmemmap is located directly before the VMALLOC region and sized
>> such that we can allocate enough pages to populate all the virtual
>> address space in the system (similar to the way it's done in arm64).
>>
>> During initialization, call memblocks_present() and sparse_init(),
>> and provide a stub for vmemmap_populate() (all of which is similar to
>> arm64).
>>
>> [greentime.hu@sifive.com:
>> fixed pfn_valid, FIXADDR_TOP and fixed a bug rebasing onto v5.3]
>> Signed-off-by: Greentime Hu <greentime.hu@sifive.com>
>> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
>> Reviewed-by: Palmer Dabbelt <palmer@sifive.com>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>> Cc: Albert Ou <aou@eecs.berkeley.edu>
>> Cc: Andrew Waterman <andrew@sifive.com>
>> Cc: Olof Johansson <olof@lixom.net>
>> Cc: Michael Clark <michaeljclark@mac.com>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Zong Li <zong@andestech.com>
>
> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
Thanks!
Logan
next prev parent reply other threads:[~2019-08-29 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 21:40 Logan Gunthorpe
2019-08-29 6:21 ` Mike Rapoport
2019-08-29 15:46 ` Logan Gunthorpe [this message]
2019-08-29 11:01 ` Christoph Hellwig
2019-08-29 23:38 ` Paul Walmsley
2019-08-29 23:41 ` Logan Gunthorpe
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=80a6c33f-6914-ee5f-7456-e1bf3d8801e0@deltatee.com \
--to=logang@deltatee.com \
--cc=andrew@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michaeljclark@mac.com \
--cc=olof@lixom.net \
--cc=palmer@sifive.com \
--cc=robh@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=sbates@raithlin.com \
--cc=zong@andestech.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
all inboxes | Powered by JetHome®