From: Cornelia Huck <cohuck@redhat.com>
To: Eric Auger <eauger@redhat.com>, Sebastian Ott <sebott@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Alireza Sanaee <alireza.sanaee@huawei.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/3] arm: handle CCSIDR_EL1 as a demuxed register
Date: Tue, 30 Jun 2026 15:49:26 +0200 [thread overview]
Message-ID: <87fr24kujd.fsf@redhat.com> (raw)
In-Reply-To: <aa1f8006-4665-4fcd-b8ee-5b90cd53e953@redhat.com>
On Mon, Jun 29 2026, Eric Auger <eauger@redhat.com> wrote:
> Hi Sebastian,
>
> On 6/22/26 3:56 PM, Sebastian Ott wrote:
(...)
>> diff --git a/target/arm/cpu-sysregs.h.inc b/target/arm/cpu-sysregs.h.inc
>> index 6e8b335b8f..d9e058a57e 100644
>> --- a/target/arm/cpu-sysregs.h.inc
>> +++ b/target/arm/cpu-sysregs.h.inc
>> @@ -39,6 +39,7 @@ DEF(MVFR2_EL1, 3, 0, 0, 3, 2)
>> DEF(ID_PFR2_EL1, 3, 0, 0, 3, 4)
>> DEF(ID_DFR1_EL1, 3, 0, 0, 3, 5)
>> DEF(ID_MMFR5_EL1, 3, 0, 0, 3, 6)
>> +DEF_MUX(CCSIDR_EL1, 3, 1, 0, 0, 0, 16)
> As I mentionned earlier, if this file were to be generated at some
> point, I don't see how I can infer the size of the muxed register from
> the AARCHMRS.
>
> Nevertheless I can move this definition somewhere else later and I think
> this shall not be a blocker for this series
Can we move this to some cpu-sysregs-demux.h.inc file? It would mess up
the order, but that should not be a problem in practice?
>
> Also I wonder if 16 is enough (although it is the current size in
> ArchCPU). In the future might end up = 8 levels x Ind 2 value x 2 value
> TnD = 32
>
> May be Tnd is not featured yet because it is relevant if FEAT_MTE2 is
> supported.
The KVM interface is also limited IIRC, so I guess it would need to be
extended.
>
>> DEF(CLIDR_EL1, 3, 1, 0, 0, 1)
>> DEF(ID_AA64ZFR0_EL1, 3, 0, 0, 4, 4)
>> DEF(CTR_EL0, 3, 3, 0, 0, 1)
next prev parent reply other threads:[~2026-06-30 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 13:56 [PATCH v3 0/3] arm: demuxed ID registers (CCSIDR_EL1) Sebastian Ott
2026-06-22 13:56 ` [PATCH v3 1/3] arm: handle demuxed ID registers Sebastian Ott
2026-06-29 14:33 ` Eric Auger
2026-06-22 13:56 ` [PATCH v3 2/3] arm: handle CCSIDR_EL1 as a demuxed register Sebastian Ott
2026-06-29 15:23 ` Eric Auger
2026-06-30 13:49 ` Cornelia Huck [this message]
2026-06-22 13:56 ` [PATCH v3 3/3] arm/kvm: get demuxed ID registers from kvm Sebastian Ott
2026-06-29 15:28 ` Eric Auger
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=87fr24kujd.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alireza.sanaee@huawei.com \
--cc=eauger@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sebott@redhat.com \
/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