From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH 5/5] powerpc/mm: Drop CONFIG_PPC_HAS_HASH_64K
Date: Mon, 10 Aug 2015 11:07:44 +0530 [thread overview]
Message-ID: <87r3nbputz.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1438928387-6454-5-git-send-email-mpe@ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> The relation between CONFIG_PPC_HAS_HASH_64K and CONFIG_PPC_64K_PAGES is
> painfully complicated.
>
> But if we rearrange it enough we can see that PPC_HAS_HASH_64K
> essentially depends on PPC_STD_MMU_64 && PPC_64K_PAGES.
>
> We can then notice that PPC_HAS_HASH_64K is used in files that are only
> built for PPC_STD_MMU_64, meaning it's equivalent to PPC_64K_PAGES.
>
> So replace all uses and drop it.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> arch/powerpc/Kconfig | 6 ------
> arch/powerpc/mm/hash_low_64.S | 4 ++--
> arch/powerpc/mm/hash_utils_64.c | 12 ++++++------
> 3 files changed, 8 insertions(+), 14 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 3a4ba2809201..1e69dee29be3 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -514,11 +514,6 @@ config NODES_SPAN_OTHER_NODES
> def_bool y
> depends on NEED_MULTIPLE_NODES
>
> -config PPC_HAS_HASH_64K
> - bool
> - depends on PPC64
> - default n
> -
> config STDBINUTILS
> bool "Using standard binutils settings"
> depends on 44x
> @@ -566,7 +561,6 @@ config PPC_16K_PAGES
> config PPC_64K_PAGES
> bool "64k page size"
> depends on !PPC_FSL_BOOK3E && (44x || PPC_STD_MMU_64 || PPC_BOOK3E_64)
> - select PPC_HAS_HASH_64K if PPC_STD_MMU_64
>
> config PPC_256K_PAGES
> bool "256k page size"
> diff --git a/arch/powerpc/mm/hash_low_64.S b/arch/powerpc/mm/hash_low_64.S
> index 463174a4a647..3b49e3295901 100644
> --- a/arch/powerpc/mm/hash_low_64.S
> +++ b/arch/powerpc/mm/hash_low_64.S
> @@ -701,7 +701,7 @@ htab_pte_insert_failure:
>
> #endif /* CONFIG_PPC_64K_PAGES */
>
> -#ifdef CONFIG_PPC_HAS_HASH_64K
> +#ifdef CONFIG_PPC_64K_PAGES
>
> /*****************************************************************************
> * *
> @@ -993,7 +993,7 @@ ht64_pte_insert_failure:
> b ht64_bail
>
>
> -#endif /* CONFIG_PPC_HAS_HASH_64K */
> +#endif /* CONFIG_PPC_64K_PAGES */
>
>
> /*****************************************************************************
> diff --git a/arch/powerpc/mm/hash_utils_64.c b/arch/powerpc/mm/hash_utils_64.c
> index 5ec987f65b2c..aee70171355b 100644
> --- a/arch/powerpc/mm/hash_utils_64.c
> +++ b/arch/powerpc/mm/hash_utils_64.c
> @@ -640,7 +640,7 @@ extern u32 ht64_call_hpte_updatepp[];
>
> static void __init htab_finish_init(void)
> {
> -#ifdef CONFIG_PPC_HAS_HASH_64K
> +#ifdef CONFIG_PPC_64K_PAGES
> patch_branch(ht64_call_hpte_insert1,
> ppc_function_entry(ppc_md.hpte_insert),
> BRANCH_SET_LINK);
> @@ -653,7 +653,7 @@ static void __init htab_finish_init(void)
> patch_branch(ht64_call_hpte_updatepp,
> ppc_function_entry(ppc_md.hpte_updatepp),
> BRANCH_SET_LINK);
> -#endif /* CONFIG_PPC_HAS_HASH_64K */
> +#endif /* CONFIG_PPC_64K_PAGES */
>
> patch_branch(htab_call_hpte_insert1,
> ppc_function_entry(ppc_md.hpte_insert),
> @@ -1151,12 +1151,12 @@ int hash_page_mm(struct mm_struct *mm, unsigned long ea,
> check_paca_psize(ea, mm, psize, user_region);
> #endif /* CONFIG_PPC_64K_PAGES */
>
> -#ifdef CONFIG_PPC_HAS_HASH_64K
> +#ifdef CONFIG_PPC_64K_PAGES
> if (psize == MMU_PAGE_64K)
> rc = __hash_page_64K(ea, access, vsid, ptep, trap,
> flags, ssize);
> else
> -#endif /* CONFIG_PPC_HAS_HASH_64K */
> +#endif /* CONFIG_PPC_64K_PAGES */
> {
> int spp = subpage_protection(mm, ea);
> if (access & spp)
> @@ -1264,12 +1264,12 @@ void hash_preload(struct mm_struct *mm, unsigned long ea,
> update_flags |= HPTE_LOCAL_UPDATE;
>
> /* Hash it in */
> -#ifdef CONFIG_PPC_HAS_HASH_64K
> +#ifdef CONFIG_PPC_64K_PAGES
> if (mm->context.user_psize == MMU_PAGE_64K)
> rc = __hash_page_64K(ea, access, vsid, ptep, trap,
> update_flags, ssize);
> else
> -#endif /* CONFIG_PPC_HAS_HASH_64K */
> +#endif /* CONFIG_PPC_64K_PAGES */
> rc = __hash_page_4K(ea, access, vsid, ptep, trap, update_flags,
> ssize, subpage_protection(mm, ea));
>
> --
> 2.1.4
next prev parent reply other threads:[~2015-08-10 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 6:19 [PATCH 1/5] powerpc/mm: Fix pte_pagesize_index() crash on 4K w/64K hash Michael Ellerman
2015-08-07 6:19 ` [PATCH 2/5] powerpc/cell: Drop support for 64K local store on 4K kernels Michael Ellerman
2015-08-10 8:14 ` Jeremy Kerr
2015-08-07 6:19 ` [PATCH 3/5] powerpc/mm: Drop the 64K on 4K version of pte_pagesize_index() Michael Ellerman
2015-08-10 5:34 ` Aneesh Kumar K.V
2015-08-07 6:19 ` [PATCH 4/5] powerpc/mm: Simplify page size kconfig dependencies Michael Ellerman
2015-08-10 5:36 ` Aneesh Kumar K.V
2015-08-07 6:19 ` [PATCH 5/5] powerpc/mm: Drop CONFIG_PPC_HAS_HASH_64K Michael Ellerman
2015-08-10 5:37 ` Aneesh Kumar K.V [this message]
2015-08-10 5:33 ` [PATCH 1/5] powerpc/mm: Fix pte_pagesize_index() crash on 4K w/64K hash Aneesh Kumar K.V
2015-08-19 23:14 ` [1/5] " Michael Ellerman
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=87r3nbputz.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.