On Tue, 3 Mar 2026 at 14:39, Eric Auger <[email protected]> wrote:
>
> As opposed to other register types, arm64 system register decoding
> is not introduced by any 'register' mention which can lead to
> unfriendly user-facing traces.  Let's add "system register"
>
> Signed-off-by: Eric Auger <[email protected]>
> ---
>  target/arm/kvm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/arm/kvm.c b/target/arm/kvm.c
> index cfb46015d48..43dab246097 100644
> --- a/target/arm/kvm.c
> +++ b/target/arm/kvm.c
> @@ -921,7 +921,7 @@ char *kvm_print_register_name(uint64_t regidx)
>          case KVM_REG_ARM_DEMUX:
>              return g_strdup_printf("demuxed reg %"PRIx64, regidx);
>          case KVM_REG_ARM64_SYSREG:
> -            return g_strdup_printf("op0:%d op1:%d crn:%d crm:%d op2:%d",
> +            return g_strdup_printf("system register op0:%d op1:%d crn:%d 
> crm:%d op2:%d",
>                                     CP_REG_ARM64_SYSREG_OP(regidx, OP0),
>                                     CP_REG_ARM64_SYSREG_OP(regidx, OP1),
>                                     CP_REG_ARM64_SYSREG_OP(regidx, CRN),
> --
> 2.53.0

Reviewed-by: Peter Maydell <[email protected]>

thanks
-- PMM

Reply via email to