From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: mike.kravetz@oracle.com, aneesh.kumar@linux.ibm.com, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] powerpc/mm/64s: Drop pgd_huge()
Date: Wed, 05 Oct 2022 00:24:14 +1100 [thread overview]
Message-ID: <166488985450.779920.10720240945227242140.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220903123640.719846-1-mpe@ellerman.id.au>
On Sat, 3 Sep 2022 22:36:39 +1000, Michael Ellerman wrote:
> On powerpc there are two ways for huge pages to be represented in the
> top level page table, aka PGD (Page Global Directory).
>
> If the address space mapped by an individual PGD entry does not
> correspond to a given huge page size, then the PGD entry points to a
> non-standard page table, known as a "hugepd" (Huge Page Directory).
> The hugepd contains some number of huge page PTEs sufficient to map the
> address space with the given huge page size.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/mm/64s: Drop pgd_huge()
https://git.kernel.org/powerpc/c/51da853e3708852f47cd95e6f5e1821c3d54c3ef
[2/2] powerpc/mm/64s: Drop p4d_leaf()
https://git.kernel.org/powerpc/c/79c5640ab4460a03535ce0f120193174e7701b65
cheers
prev parent reply other threads:[~2022-10-04 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 12:36 Michael Ellerman
2022-09-03 12:36 ` [PATCH 2/2] powerpc/mm/64s: Drop p4d_leaf() Michael Ellerman
2022-09-03 15:11 ` Christophe Leroy
2022-09-04 11:32 ` Michael Ellerman
2022-09-04 16:57 ` Aneesh Kumar K.V
2022-09-03 15:06 ` [PATCH 1/2] powerpc/mm/64s: Drop pgd_huge() Christophe Leroy
2022-09-04 11:24 ` Michael Ellerman
2022-09-04 16:57 ` Aneesh Kumar K.V
2022-10-04 13:24 ` Michael Ellerman [this message]
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=166488985450.779920.10720240945227242140.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mike.kravetz@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox