From: christophe leroy <christophe.leroy@c-s.fr>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Scott Wood <oss@buserror.net>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 6/6] powerpc/8xx: implementation of huge pages
Date: Sun, 14 Aug 2016 19:38:47 +0200 [thread overview]
Message-ID: <55f9f338-a098-96e0-c753-2e83045bedab@c-s.fr> (raw)
In-Reply-To: <8760r3a0md.fsf@skywalker.in.ibm.com>
Le 14/08/2016 à 16:25, Aneesh Kumar K.V a écrit :
> Christophe Leroy <christophe.leroy@c-s.fr> writes:
>
>> The 8xx has 512k and 8M pages. This patch implements hugepages using
>> those sizes.
>>
>> On the 8xx, the size of pages is in the PGD entry,
>> using PS field (bits 28-29):
>> 00 : Small pages (4k or 16k)
>> 01 : 512k pages
>> 10 : reserved
>> 11 : 8M pages
>>
>> The implementation uses a mix of what is used on BOOKS and BOOKE,
>> as 512k pages are in HUGEPTE tables while for 8M pages we have
>> several PGD entries pointing on a leaf HUGEPTE entry
>>
>> For the time being, we do not support CPU15 ERRATA if HUGETLB is
>> selected
>
> Can you also document here the format for linux page table with different
> huge page size. ?
Euh ... isn't it what I do when explaining the use of the PS field in
the PGD entry ? That's the thing, that's how the 8xx knows how it is a
huge page, and that's how Linux will know it is one. On the 8xx, the
Linux PGD entry (almost) match the L1 MMU entry and the Linux PTE almost
match the L2 MMU entry (some bits are copied from the PTE to the L1
entry and then removed from the value writen to the L2 MMU entry)
Christophe
>
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2016-08-14 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 16:55 [PATCH 0/6] powerpc/8xx: implementation of huge pages Christophe Leroy
2016-08-12 16:55 ` [PATCH 1/6] powerpc: port 64 bits pgtable_cache to 32 bits Christophe Leroy
2016-08-14 14:17 ` Aneesh Kumar K.V
2016-08-14 18:51 ` christophe leroy
2016-08-15 10:23 ` Aneesh Kumar K.V
2016-08-12 16:55 ` [PATCH 2/6] powerpc: fix usage of _PAGE_RO in hugepage Christophe Leroy
2016-08-12 16:55 ` [PATCH 3/6] powerpc/8xx: use r3 to scratch CR in ITLBmiss Christophe Leroy
2016-08-12 16:55 ` [PATCH 4/6] powerpc/8xx: Move additional DTLBMiss handlers out of exception area Christophe Leroy
2016-08-12 16:55 ` [PATCH 5/6] powerpc/8xx: make user addr DTLB miss the short path Christophe Leroy
2016-08-12 16:55 ` [PATCH 6/6] powerpc/8xx: implementation of huge pages Christophe Leroy
2016-08-14 14:25 ` Aneesh Kumar K.V
2016-08-14 17:38 ` christophe leroy [this message]
2016-08-15 10:30 ` Aneesh Kumar K.V
2016-08-14 14:27 ` [PATCH 0/6] " Aneesh Kumar K.V
2016-08-14 17:33 ` christophe leroy
2016-08-15 10:31 ` 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=55f9f338-a098-96e0-c753-2e83045bedab@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--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).