From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/4] target/arm: Add ID_AA64MMFR2_EL1
Date: Sat, 1 Feb 2020 16:54:15 -0800 [thread overview]
Message-ID: <d7fc8b19-e004-cf10-c2a0-58f38371c5ac@linaro.org> (raw)
In-Reply-To: <CAFEAcA9wOmOdddzr+5RfBsTJ+nHF4bqTVs0C1Uj228f28U_SMA@mail.gmail.com>
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~
next prev parent reply other threads:[~2020-02-02 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 23:42 [PATCH 0/4] target/arm: Implement ARMv8.2-UAO Richard Henderson
2019-12-03 23:42 ` [PATCH 1/4] target/arm: Add ID_AA64MMFR2_EL1 Richard Henderson
2019-12-06 18:19 ` Peter Maydell
2020-02-02 0:54 ` Richard Henderson [this message]
2019-12-03 23:42 ` [PATCH 2/4] target/arm: Update MSR access to UAO Richard Henderson
2019-12-06 18:30 ` Peter Maydell
2019-12-06 19:00 ` Richard Henderson
2020-02-02 1:00 ` Richard Henderson
2020-02-02 13:29 ` Peter Maydell
2020-02-03 7:46 ` Richard Henderson
2019-12-03 23:42 ` [PATCH 3/4] target/arm: Implement UAO semantics Richard Henderson
2019-12-06 18:31 ` Peter Maydell
2019-12-03 23:42 ` [PATCH 4/4] target/arm: Enable ARMv8.2-UAO in -cpu max Richard Henderson
2019-12-06 18:31 ` Peter Maydell
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=d7fc8b19-e004-cf10-c2a0-58f38371c5ac@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).