From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org, oohall@gmail.com
Subject: Re: [PATCH 0/2] Enable ZONE_DEVICE on POWER
Date: Fri, 06 May 2016 10:43:37 +0530 [thread overview]
Message-ID: <572C2801.7050605@linux.vnet.ibm.com> (raw)
In-Reply-To: <87r3dgk1bh.fsf@skywalker.in.ibm.com>
On 05/05/2016 08:18 PM, Aneesh Kumar K.V wrote:
> Anshuman Khandual <khandual@linux.vnet.ibm.com> writes:
>
>> This enables base ZONE_DEVICE support on POWER. This series depends on
>> the following patches posted by Oliver.
>>
>> https://patchwork.ozlabs.org/patch/618867/
>> https://patchwork.ozlabs.org/patch/618868/
>>
>> Anshuman Khandual (2):
>> powerpc/mm: Make vmemmap_populate accommodate ZONE_DEVICE memory
>> powerpc/mm: Enable support for ZONE_DEVICE on PPC_BOOK3S_64 platforms
>>
>> arch/powerpc/mm/init_64.c | 4 +++-
>> mm/Kconfig | 2 +-
>> 2 files changed, 4 insertions(+), 2 deletions(-)
>>
>
> What is the use case ? Who will use ZONE_DEVICE on ppc64. This should be
> be merged along with the patch series that use this.
IIUC, Oliver has been looking at using ZONE_DEVICE for the NVDIMM (or
some other persistent memory) drivers. I have been following Dan William's
work on this front and want to explore more details about it's functioning
on ppc64. This enablement will just help us little bit in that direction.
next prev parent reply other threads:[~2016-05-06 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 12:11 [PATCH 0/2] Enable ZONE_DEVICE on POWER Anshuman Khandual
2016-05-05 12:11 ` [PATCH 1/2] powerpc/mm: Make vmemmap_populate accommodate ZONE_DEVICE memory Anshuman Khandual
2016-05-05 12:11 ` [PATCH 2/2] powerpc/mm: Enable support for ZONE_DEVICE on PPC_BOOK3S_64 platforms Anshuman Khandual
2016-05-05 14:48 ` [PATCH 0/2] Enable ZONE_DEVICE on POWER Aneesh Kumar K.V
2016-05-06 5:13 ` Anshuman Khandual [this message]
2016-05-06 6:14 ` oliver
2016-05-08 17:37 ` Aneesh Kumar K.V
2016-05-10 7:12 ` Anshuman Khandual
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=572C2801.7050605@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=oohall@gmail.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).