From: Paul Walmsley <paul.walmsley@sifive.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Greentime Hu <green.hu@gmail.com>, Rob Herring <robh@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Waterman <andrew@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Bates <sbates@raithlin.com>,
Olof Johansson <olof@lixom.net>,
greentime.hu@sifive.com, linux-riscv@lists.infradead.org,
Michael Clark <michaeljclark@mac.com>,
Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org
Subject: Re: [PATCH v4 2/2] RISC-V: Implement sparsemem
Date: Tue, 13 Aug 2019 09:48:43 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908130947130.30024@viisi.sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908130921170.30024@viisi.sifive.com>
On Tue, 13 Aug 2019, Paul Walmsley wrote:
> On Tue, 13 Aug 2019, Logan Gunthorpe wrote:
>
> > On 2019-08-13 12:04 a.m., Greentime Hu wrote:
> >
> > > Every architecture with mmu defines their own pfn_valid().
> >
> > Not true. Arm64, for example just uses the generic implementation in
> > mmzone.h.
>
> arm64 seems to define their own:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/Kconfig#n899
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/mm/init.c#n235
>
> While there are many architectures which have their own pfn_valid();
> oddly, almost none of them set HAVE_ARCH_PFN_VALID ?
(fixed the linux-mm@ address)
- Paul
parent reply other threads:[~2019-08-13 16:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.21.9999.1908130921170.30024@viisi.sifive.com>]
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=alpine.DEB.2.21.9999.1908130947130.30024@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=andrew@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=green.hu@gmail.com \
--cc=greentime.hu@sifive.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=michaeljclark@mac.com \
--cc=olof@lixom.net \
--cc=palmer@sifive.com \
--cc=robh@kernel.org \
--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