> On 27 May 2026, at 9:31 PM, Eric Auger <[email protected]> wrote:
>
> but if a field is RESx why don't you want to overwrite it? Are there
> cases where a field is RESx depending on a condition?
>
> Thanks
>
> Eric
>
There are cases where fields are RESx based on conditions.
but too complex to get into those (CCSIDR for e.g.).
What I meant is when we want to realize a model,
1. If we don’t account for RESx fields how will we know which fields Res0 or
Res1.
2. In future what if RESx field becomes a defined field? Instead of maintaining:
>
>
> + if ((!strcmp(reg->name, "ID_ISAR0_EL1") && i >= 28 && i <= 31) || /*
> RES0 */
> + (!strcmp(reg->name, "ID_ISAR5_EL1") && i >= 20 && i <= 23) || /*
> RES0 */
> + (!strcmp(reg->name, "MVFR2_EL1") && i >= 8 && i <= 31) || /* RES0 */
> + (!strcmp(reg->name, "ID_PFR2_EL1") && i >= 12 && i <= 31) || /* RES0
> */
> + (!strcmp(reg->name, "ID_MMFR5_EL1") && i >= 8 && i <= 31) || /* RES0
> */
> + (!strcmp(reg->name, "ID_AA64FPFR0_EL1") && i >= 2 && i <= 7)) { /*
> RAZ */
> + return true;
> + }
We can just maintain one cpu-idregs.h.inc and have RESx in that.
Warm Regards,
Khushit
