Re: [PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values

2022-10-28 Thread Catalin Marinas
On Fri, Oct 28, 2022 at 10:18:41AM +0800, Zenghui Yu wrote: > On 2022/8/26 20:00, Anders Roxell wrote: > > On 2021-03-10 11:23, Anshuman Khandual wrote: > > > From: James Morse > > > > > > As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, > > > ID_AA64MMFR0_EL1 > > > might contain a

Re: [PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values

2022-10-27 Thread Zenghui Yu
On 2022/8/26 20:00, Anders Roxell wrote: On 2021-03-10 11:23, Anshuman Khandual wrote: From: James Morse As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, ID_AA64MMFR0_EL1 might contain a range of values to describe supported translation granules (4K and 16K pages sizes in

Re: [PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values

2022-08-26 Thread Anders Roxell
On 2021-03-10 11:23, Anshuman Khandual wrote: > From: James Morse > > As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, ID_AA64MMFR0_EL1 > might contain a range of values to describe supported translation granules > (4K and 16K pages sizes in particular) instead of just enabled or

Re: [PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values

2021-03-10 Thread Will Deacon
On Wed, 10 Mar 2021 11:23:10 +0530, Anshuman Khandual wrote: > As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, ID_AA64MMFR0_EL1 > might contain a range of values to describe supported translation granules > (4K and 16K pages sizes in particular) instead of just enabled or disabled >

[PATCH V2] arm64/mm: Fix __enable_mmu() for new TGRAN range values

2021-03-09 Thread Anshuman Khandual
From: James Morse As per ARM ARM DDI 0487G.a, when FEAT_LPA2 is implemented, ID_AA64MMFR0_EL1 might contain a range of values to describe supported translation granules (4K and 16K pages sizes in particular) instead of just enabled or disabled values. This changes __enable_mmu() function to