Re: [PATCH V3] arm64/cpufeature: Validate hypervisor capabilities during CPU hotplug

On 05/20/2020 11:24 PM, Will Deacon wrote: > On Tue, 12 May 2020 07:27:27 +0530, Anshuman Khandual wrote: >> This validates hypervisor capabilities like VMID width, IPA range for any >> hot plug CPU against system finalized values. KVM's view of the IPA space >> is used while allowing a given

Re: [PATCH V2] arm64/cpufeature: Drop open encodings while extracting parange

On Wed, 13 May 2020 14:33:34 +0530, Anshuman Khandual wrote: > Currently there are multiple instances of parange feature width mask open > encodings while fetching it's value. Even the width mask value (0x7) itself > is not accurate. It should be (0xf) per ID_AA64MMFR0_EL1.PARange[3:0] as in > ARM

Re: [PATCH V3] arm64/cpufeature: Validate hypervisor capabilities during CPU hotplug

On Tue, 12 May 2020 07:27:27 +0530, Anshuman Khandual wrote: > This validates hypervisor capabilities like VMID width, IPA range for any > hot plug CPU against system finalized values. KVM's view of the IPA space > is used while allowing a given CPU to come up. While here, it factors out >

Re: [PATCH V2] arm64/cpufeature: Drop open encodings while extracting parange

On Wed, 13 May 2020 14:33:34 +0530 Anshuman Khandual wrote: > Currently there are multiple instances of parange feature width mask open > encodings while fetching it's value. Even the width mask value (0x7) itself > is not accurate. It should be (0xf) per ID_AA64MMFR0_EL1.PARange[3:0] as in >