Re: [PATCH 2/2] powerpc/mm/64s: Drop p4d_leaf()

2022-09-04 Thread Aneesh Kumar K.V
Michael Ellerman writes: > > Because 64-bit Book3S uses pgtable-nop4d.h, the P4D is folded into the > PGD. So P4D entries are actually PGD entries, or vice versa. > > The other way to think of it is that the P4D is a single entry page > table below the PGD. Zero bits of the address are needed to

Re: [PATCH 2/2] powerpc/mm/64s: Drop p4d_leaf()

2022-09-04 Thread Michael Ellerman
Christophe Leroy writes: > Le 03/09/2022 à 14:36, Michael Ellerman a écrit : >> Because 64-bit Book3S uses pgtable-nop4d.h, the P4D is folded into the >> PGD. So P4D entries are actually PGD entries, or vice versa. >> >> The other way to think of it is that the P4D is a single entry page >> table

Re: [PATCH 2/2] powerpc/mm/64s: Drop p4d_leaf()

2022-09-03 Thread Christophe Leroy
Le 03/09/2022 à 14:36, Michael Ellerman a écrit : > Because 64-bit Book3S uses pgtable-nop4d.h, the P4D is folded into the > PGD. So P4D entries are actually PGD entries, or vice versa. > > The other way to think of it is that the P4D is a single entry page > table below the PGD. Zero bits of th

[PATCH 2/2] powerpc/mm/64s: Drop p4d_leaf()

2022-09-03 Thread Michael Ellerman
Because 64-bit Book3S uses pgtable-nop4d.h, the P4D is folded into the PGD. So P4D entries are actually PGD entries, or vice versa. The other way to think of it is that the P4D is a single entry page table below the PGD. Zero bits of the address are needed to index into the P4D, therefore a P4D en