Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2D4D7316192 for ; Tue, 16 Jun 2026 13:26:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781616404; cv=none; b=sAHjHCVHaPG91vUxSASfkTATNs+1gmAS7TQsB8upS4SC0DpUgcZyRh5NPbNpR738cudYroqkMnRZdrlQUeUf40YUW7akPBbnTxk6NfgKxWMaTl8WsHzZ8VK+SzBrPzczdXY3cBHqg8auC4eI+8YjvLqVBCZJN1glW4X3A/3U7ik= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781616404; c=relaxed/simple; bh=TPhOEshpLAyFJyerj7yOiHshvRfYFUVhsi1RzQ+8tgM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:content-type; b=c4081XR9enNsQ9sXOTNlWHziM9RX2kjJ2zlMDkD09jBEfA0MZjJEsO1C9o6uTO9M6bhhdiVbm+5VybwjR5Nn7nNPavVUm8s9L0+aSnnMSDyLutX4CTpqSZAk/bUd9c05kblT75JSn/hZPgkBmeX8IGDDT59CmmIe96vNqV9us0I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=Gpcc5kXd; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Gpcc5kXd" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1781616402; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=OCTYHIVEWuGrk0Rhta/8oenK8fxSIqUARq5vxMjeiVI=; b=Gpcc5kXdcY2jvL4P4gDK2HWCl8YccjKDzu3INYyyxuRO6VPm+r5Vr0xEey3xzDe9n+VgHJ wVL7gLn/A8xoVFPs2iDfMASJVLY6wWkrwgS0aT/Bl56cllQ3P/E6cxgvnglHVQ2EWIO8nX ViYebLaCu1zKgY8xSUhf0hBC7agr5UY= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-205-2Yi3HbraNzyf9Xad4hel7Q-1; Tue, 16 Jun 2026 09:26:38 -0400 X-MC-Unique: 2Yi3HbraNzyf9Xad4hel7Q-1 X-Mimecast-MFC-AGG-ID: 2Yi3HbraNzyf9Xad4hel7Q_1781616396 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 8616C19560A5; Tue, 16 Jun 2026 13:26:36 +0000 (UTC) Received: from laptop.redhat.com (unknown [10.44.48.30]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 910A13000203; Tue, 16 Jun 2026 13:26:29 +0000 (UTC) From: Eric Auger To: eric.auger.pro@gmail.com, eric.auger@redhat.com, qemu-devel@nongnu.org, qemu-arm@nongnu.org, kvmarm@lists.linux.dev, peter.maydell@linaro.org, shaju.abraham@nutanix.com, khushit.shah@nutanix.com, yangjinqian1@huawei.com, cohuck@redhat.com, richard.henderson@linaro.org, sebott@redhat.com, skolothumtho@nvidia.com, philmd@linaro.org Cc: maz@kernel.org, oliver.upton@linux.dev, pbonzini@redhat.com, armbru@redhat.com, berrange@redhat.com, abologna@redhat.com, jdenemar@redhat.com Subject: [RFC PATCH v6 00/17] kvm/arm: Introduce a customizable aarch64 KVM host model Date: Tue, 16 Jun 2026 15:16:47 +0200 Message-ID: <20260616132625.1732031-1-eric.auger@redhat.com> Precedence: bulk X-Mailing-List: kvmarm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-MFC-PROC-ID: NPYHzgYdFn8aBS7ied-G_4UMtJgMUGxqxfRjL7BcndI_1781616396 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true This series enhances the current host KVM model with capability to set writable ID reg fields. Since v6.7 kernel, KVM/arm allows the userspace to overwrite the values of a subset of ID regs. The list of writable fields continues to grow. The feature ID range is defined as the AArch64 System register space with op0==3, op1=={0, 1, 3}, CRn==0, CRm=={0-7}, op2=={0-7}. The end goal is to get more flexibility when migrating guests between different host hardware. QEMU retrieves the writable ID fields from KVM UAPI [1] and match them against a generated description of ID regs and their named fields that stem from AARCHMRS Registers.json file. Current description is based on latest 2026-03 edition. The content of the generated files was compared against kernel linux/arch/arm64/tools/sysreg file. It is not straightforward to have unit tests for python scripts as there are many cases for field extraction. For each writable named field a uint64 property is created following the "SYSREG__" naming convention. REG and FIELD names are those described in ARM ARM Reference manual. The list of SYSREG_ID properties can be retrieved through the qmp monitor using query-cpu-model-expansion [2]. For the record, Jinqian was able to migrate between Hisilicon KunPeng HIP09 and HIP12 chips with this series using this kind of command: -cpu host,pauth=off,pmu=off,sve=off,\ SYSREG_ID_AA64PFR1_EL1_NMI=0x0,\ SYSREG_ID_AA64ISAR1_EL1_LS64=0x0,\ SYSREG_ID_AA64ISAR1_EL1_XS=0x0,\ SYSREG_ID_AA64ISAR1_EL1_LRCPC=0x2,\ SYSREG_ID_AA64ISAR2_EL1_RPRFM=0x0,\ SYSREG_ID_AA64ISAR2_EL1_CLRBHB=0x0,\ SYSREG_ID_AA64ISAR2_EL1_PAC_frac=0x0,\ SYSREG_ID_AA64ISAR2_EL1_BC=0x0,\ SYSREG_ID_AA64ISAR2_EL1_RPRES=0x0,\ SYSREG_ID_AA64ISAR2_EL1_WFxT=0x0,\ SYSREG_ID_AA64MMFR0_EL1_FGT=0x0,\ SYSREG_ID_AA64MMFR0_EL1_BigEnd=0x0,\ SYSREG_ID_AA64MMFR1_EL1_ECBHB=0x0,\ SYSREG_ID_AA64MMFR1_EL1_CMOW=0x0,\ SYSREG_ID_AA64MMFR1_EL1_TIDCP1=0x0,\ SYSREG_ID_AA64MMFR1_EL1_nTLBPA=0x0,\ SYSREG_ID_AA64MMFR1_EL1_AFP=0x0,\ SYSREG_ID_AA64MMFR1_EL1_HCX=0x0,\ SYSREG_ID_AA64MMFR1_EL1_ETS=0x0,\ SYSREG_ID_AA64MMFR1_EL1_PAN=0x2,\ SYSREG_ID_AA64MMFR1_EL1_HAFDBS=0x2,\ SYSREG_ID_AA64MMFR2_EL1_CnP=0x0,\ SYSREG_ID_AA64MMFR3_EL1_TCRX=0x0,\ SYSREG_ID_AA64DFR0_EL1_PMUVer=0x6,\ SYSREG_ID_AA64DFR0_EL1_DebugVer=0x9,\ SYSREG_ID_AA64DFR0_EL1_DoubleLock=0xf,\ SYSREG_ID_AA64ZFR0_EL1_F64MM=0x0,\ SYSREG_ID_AA64ZFR0_EL1_F32MM=0x0,\ SYSREG_ID_AA64ZFR0_EL1_SM4=0x0,\ SYSREG_ID_AA64ZFR0_EL1_SHA3=0x0,\ SYSREG_ID_AA64ZFR0_EL1_BitPerm=0x0,\ SYSREG_ID_AA64ZFR0_EL1_AES=0x0,\ SYSREG_ID_AA64ZFR0_EL1_SVEver=0x0,\ SYSREG_CTR_EL0_L1Ip=0x2 \ Connie & Eric This series can be found at: https://github.com/eauger/qemu/tree/arm-cpu-model-v6 History: -------- v5 -> v6: v6 is mostly for Khushit to see how he may work on top of this series. It fulfills some of his requirements: - Upon Khushit request I added description for enum values and reserved fields - set_sysreg_prop checks the input value against enum values if any - writable_bitmap is now dispatched into the sysreg descripton and not stored in vcpu state anymore (besides it is VM wide) - implemented write for qmp inspection. However this is not yet checked against KVM. That's the next step I think, ie. instantiate a scratch vcpu to test if the field value can be applied? - if some inconsistencies between writable mask and idreg field, reserved fields only produce traces - simplify checks related to availability of writable map - this version does not yet fix some reported issues about host supporting nested virt. I will further sync with Khushit. so this is definitively not candidate to be applied, hence the RFC tag. v4 -> v5: - generate target/arm/cpu-idregs.h.inc that look similar to the format used in [RFC PATCH v1 02/13] target/arm: named_cpu_model: Add ID Register Fields without the description of the value values nor safe policy/value. I guess valid values could be generated from the Registers.json file too. Safe policy/values cannot. I reused one patch from the above series. Let's see how both series can progress/coexist without any anticipated bias. - Addressed all comments from Shameer on v4 - Addressed 2 comments from v4 that were missed including the issue of IDreg visibility affected by some other settings. Unfortunately I was not able to test it. - Further look at overrides between low level id reg field properties versus legacy CPU options. I have the feeling they can coexist as long as we document the hierarchy between them: host kvm default -> ID reg field props -> legacy CPU options - Noticed more writable fields that are RES0/RAZ - Improved commit messages in general References: ----------- [1] KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES KVM_ARM_GET_REG_WRITABLE_MASKS Documentation/virt/kvm/api.rst [2] qemu-system-aarch64 -qmp unix:/home/augere/TEST/QEMU/qmp-sock,server,nowait -M virt --enable-kvm -cpu host sudo build/run qmp-shell /home/augere/TEST/QEMU/qmp-sock Welcome to the QMP low-level shell! Connected to QEMU 11.0.50 (QEMU) query-cpu-model-expansion type=full model={"name":"host"} Cornelia Huck (3): target/arm/kvm: Retrieve writable ID reg map arm-qmp-cmds: introspection for ID register props arm/cpu-features: document ID reg properties Eric Auger (13): scripts: introduce scripts/update-aarch64-cpu-sysregs-header.py target/arm/cpu-sysregs.h.inc: Sort by name alphabetical order target/arm/cpu-sysregs.h.inc: Update with automatic generation arm/cpu: Add infra to handle generated ID register definitions scripts: Introduce scripts/aarch64_sysreg_helpers module scripts: Introduce scripts/update-aarch64-cpu-sysreg-properties.py target/arm/cpu-idregs.h.inc: generate with script target/arm/cpu-idregs.h.inc: Generate enum values arm/kvm: Initialize all writable ID registers from host target/arm/kvm: Introduce kvm_arm_expose_idreg_properties target/arm/cpu: Expose writable ID reg field properties on the kvm host vcpu model target/arm/cpu-idregs.h.inc: Generate reserved fields target/arm/kvm: Ignore and trace unexpected writable reserved fields Shaju Abraham (1): target/arm/cpu_idregs: generate tables for Arm64 ID registers and fields docs/system/arm/cpu-features.rst | 106 +- target/arm/cpu-idregs.h | 41 + target/arm/kvm_arm.h | 10 + target/arm/cpu-idregs.h.inc | 2164 +++++++++++++++++ target/arm/cpu-sysregs.h.inc | 57 +- target/arm/arm-qmp-cmds.c | 29 + target/arm/cpu-idregs.c | 96 + target/arm/cpu64.c | 5 + target/arm/kvm.c | 311 ++- scripts/aarch64_sysreg_helpers.py | 109 + .../update-aarch64-cpu-sysreg-properties.py | 290 +++ scripts/update-aarch64-cpu-sysregs-header.py | 51 + target/arm/meson.build | 1 + target/arm/trace-events | 7 + 14 files changed, 3244 insertions(+), 33 deletions(-) create mode 100644 target/arm/cpu-idregs.h create mode 100644 target/arm/cpu-idregs.h.inc create mode 100644 target/arm/cpu-idregs.c create mode 100644 scripts/aarch64_sysreg_helpers.py create mode 100644 scripts/update-aarch64-cpu-sysreg-properties.py create mode 100755 scripts/update-aarch64-cpu-sysregs-header.py -- 2.53.0