From: Ram Pai <linuxram@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config
Date: Thu, 8 Feb 2018 11:22:01 -0800 [thread overview]
Message-ID: <20180208192201.GA5559@ram.oc3035372033.ibm.com> (raw)
In-Reply-To: <20180208103442.22045-1-aneesh.kumar@linux.vnet.ibm.com>
On Thu, Feb 08, 2018 at 04:04:41PM +0530, Aneesh Kumar K.V wrote:
> To support memory keys, we moved the hash pte slot information to the second
> half of the page table. This was ok with PTE entries at level 4 and level 3.
> We already allocate larger page table pages at those level to accomodate extra
> details. For level 4 we already have the extra space which was used to track
> 4k hash page table entry details and at pmd level the extra space was allocated
> to track the THP details.
>
> With hugetlbfs PTE, we used this extra space at the PMD level to store the
> slot details. But we also support hugetlbfs PTE at PUD leve and PUD level page
> didn't allocate extra space. This resulted in memory corruption.
>
> Fix this by allocating extra space at PUD level when HUGETLB is enabled. We
> may need further changes to allocate larger space at PMD level when we enable
> HUGETLB. That will be done in next patch.
>
> Fixes:bf9a95f9a6481bc6e(" powerpc: Free up four 64K PTE bits in 64K backed HPTE pages")
hmm.. did not know that hugetlbs operated at the PUD level. Thanks for
catching this.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> NOTE: In the long run we may want to look at my patch series to remove slot
...snip...
> }
>
> static inline pmd_t *pmd_alloc_one(struct mm_struct *mm, unsigned long addr)
> diff --git a/arch/powerpc/include/asm/book3s/64/pgtable.h b/arch/powerpc/include/asm/book3s/64/pgtable.h
> index 51017726d495..3c14663d457d 100644
> --- a/arch/powerpc/include/asm/book3s/64/pgtable.h
> +++ b/arch/powerpc/include/asm/book3s/64/pgtable.h
> @@ -232,11 +232,13 @@ extern unsigned long __pmd_index_size;
> extern unsigned long __pud_index_size;
> extern unsigned long __pgd_index_size;
> extern unsigned long __pmd_cache_index;
> +extern unsigned long __pud_cache_index;
> #define PTE_INDEX_SIZE __pte_index_size
> #define PMD_INDEX_SIZE __pmd_index_size
> #define PUD_INDEX_SIZE __pud_index_size
> #define PGD_INDEX_SIZE __pgd_index_size
> #define PMD_CACHE_INDEX __pmd_cache_index
> +#define PUD_CACHE_INDEX __pmd_cache_index
This is a typo. Should be 'pud' not a 'pmd'.
#define PUD_CACHE_INDEX __pud_cache_index
^
> /*
> * Because of use of pte fragments and THP, size of page table
..snip...
RP
next prev parent reply other threads:[~2018-02-08 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:34 [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config Aneesh Kumar K.V
2018-02-08 10:34 ` [PATCH 2/2] powerpc/mm/hash64: Allocate larger PMD table if hugetlb config is enabled Aneesh Kumar K.V
2018-02-08 15:16 ` [PATCH 1/2] powerpc/mm: Fix crashes with PUD level hugetlb config Aneesh Kumar K.V
2018-02-08 19:29 ` Ram Pai
2018-02-09 15:31 ` Aneesh Kumar K.V
2018-02-10 9:47 ` Aneesh Kumar K.V
2018-02-10 16:50 ` Ram Pai
2018-02-10 17:14 ` Aneesh Kumar K.V
2018-02-08 19:22 ` Ram Pai [this message]
2018-02-09 15:30 ` Aneesh Kumar K.V
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=20180208192201.GA5559@ram.oc3035372033.ibm.com \
--to=linuxram@us.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).