[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/4] target/arm: Add ID_AA64MMFR2_EL1
From: |
Richard Henderson |
Subject: |
Re: [PATCH 1/4] target/arm: Add ID_AA64MMFR2_EL1 |
Date: |
Sat, 1 Feb 2020 16:54:15 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 12/6/19 10:19 AM, Peter Maydell wrote:
>> @@ -549,6 +549,8 @@ bool kvm_arm_get_host_cpu_features(ARMHostCPUFeatures
>> *ahcf)
>> ARM64_SYS_REG(3, 0, 0, 7, 0));
>> err |= read_sys_reg64(fdarray[2], &ahcf->isar.id_aa64mmfr1,
>> ARM64_SYS_REG(3, 0, 0, 7, 1));
>> + err |= read_sys_reg64(fdarray[2], &ahcf->isar.id_aa64mmfr2,
>> + ARM64_SYS_REG(3, 0, 0, 7, 2));
>
> Do current KVM kernels definitely handle the request for this
> new register (ie don't return an error)?
Yes, ID_AA64MMFR2 was added to the sys_regs table in the same commit
(93390c0a1b20b) as all of the others here.
r~
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [PATCH 1/4] target/arm: Add ID_AA64MMFR2_EL1,
Richard Henderson <=