From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 6/7] powerpc/hugetlb: Add code to support to follow huge page directory entries
Date: Wed, 12 Apr 2017 10:18:19 +0530 [thread overview]
Message-ID: <84b5c71d-e953-aabd-c7fd-137dcc0ea643@linux.vnet.ibm.com> (raw)
In-Reply-To: <87shlfutp6.fsf@concordia.ellerman.id.au>
On 04/11/2017 03:55 PM, Michael Ellerman wrote:
> "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
>
>> Add follow_huge_pd implementation for ppc64.
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> ---
>> arch/powerpc/mm/hugetlbpage.c | 42 ++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 42 insertions(+)
>>
>> diff --git a/arch/powerpc/mm/hugetlbpage.c b/arch/powerpc/mm/hugetlbpage.c
>> index 80f6d2ed551a..9d66d4f810aa 100644
>> --- a/arch/powerpc/mm/hugetlbpage.c
>> +++ b/arch/powerpc/mm/hugetlbpage.c
>> @@ -17,6 +17,8 @@
>> #include <linux/memblock.h>
>> #include <linux/bootmem.h>
>> #include <linux/moduleparam.h>
>> +#include <linux/swap.h>
>> +#include <linux/swapops.h>
>> #include <asm/pgtable.h>
>> #include <asm/pgalloc.h>
>> #include <asm/tlb.h>
>> @@ -618,6 +620,10 @@ void hugetlb_free_pgd_range(struct mmu_gather *tlb,
>> }
>>
>> /*
>> + * 64 bit book3s use generic follow_page_mask
>> + */
>> +#ifndef CONFIG_PPC_BOOK3S_64
> I think it's always easier to follow if you use:
>
> #ifdef x
> ...
> #else /* !x */
> ...
> #endif
>
> ie. in this case put the Book3S 64 case first and the existing code in the
> #else.
Yeah, it was difficult to read in the first glance.
next prev parent reply other threads:[~2017-04-12 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 14:04 [RFC PATCH 1/7] mm/hugetlb/migration: Use set_huge_pte_at instead of set_pte_at Aneesh Kumar K.V
2017-04-04 14:04 ` [RFC PATCH 2/7] mm/follow_page_mask: Split follow_page_mask to smaller functions Aneesh Kumar K.V
2017-04-07 11:04 ` Anshuman Khandual
2017-04-04 14:04 ` [RFC PATCH 3/7] mm/hugetlb: export hugetlb_entry_migration helper Aneesh Kumar K.V
2017-04-07 11:07 ` Anshuman Khandual
2017-04-04 14:04 ` [RFC PATCH 4/7] mm/follow_page_mask: Add support for hugepage directory entry Aneesh Kumar K.V
2017-04-07 11:37 ` Anshuman Khandual
2017-04-04 14:04 ` [RFC PATCH 5/7] mm/follow_page_mask: Add support for hugetlb pgd entries Aneesh Kumar K.V
2017-04-07 11:56 ` Anshuman Khandual
2017-04-04 14:04 ` [RFC PATCH 6/7] powerpc/hugetlb: Add code to support to follow huge page directory entries Aneesh Kumar K.V
2017-04-11 10:25 ` Michael Ellerman
2017-04-12 4:48 ` Anshuman Khandual [this message]
2017-04-04 14:04 ` [RFC PATCH 7/7] powerpc/hugetlb: Enable hugetlb migration for ppc64 Aneesh Kumar K.V
2017-04-07 12:26 ` Anshuman Khandual
2017-04-04 14:07 ` [RFC PATCH 1/7] mm/hugetlb/migration: Use set_huge_pte_at instead of set_pte_at Aneesh Kumar K.V
2017-04-05 11:51 ` Anshuman Khandual
2017-04-05 15:23 ` Aneesh Kumar K.V
2017-04-07 10:59 ` 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=84b5c71d-e953-aabd-c7fd-137dcc0ea643@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).