target/riscv: add missing named features
v2 cover target/riscv: add missing named features
Hi,
In this version I fixed the problems caused in bios-table-test qtest by patches 1 and 2.
A small change was also made in patch 1 to avoid spamming "Disabling sdtrig due to priv spec version" warnings when running vendor CPUs with priv spec < 1.12.
Patches based on alistair/riscv-to-apply.next.
Changes from v1:
- patch 1:
- skip the warning and disable of 'sdtrig' for CPUs that have priv
version < 1.12
- update bios-table-test
- patch 2:
- update bios-table-test
- v1 link: https://lore.kernel.org/qemu-riscv/[email protected]/
Daniel Henrique Barboza (3):
target/riscv/cpu.c: add 'sdtrig' in riscv,isa target/riscv/cpu.c: add 'ssstrict' to riscv,isa target/riscv/cpu.c: do better with 'named features' doc
target/riscv/cpu.c | 16 ++++++++++++++-- target/riscv/tcg/tcg-cpu.c | 9 +++++++++ tests/data/acpi/riscv64/virt/RHCT | Bin 400 -> 416 bytes 3 files changed, 23 insertions(+), 2 deletions(-)
Signature · 1 line
2.49.0
PATCH v2 1/3 target/riscv/tcg: restrict satp_mode changes in cpu_set_profile
We're changing 'mmu' to true regardless of whether the profile is being enabled or not, and at the same time we're changing satp_mode to profile->enabled.
This will promote a situation where we'll set mmu=on without a virtual memory mode, which is a mistake.
Only touch 'mmu' and satp_mode if the profile is being enabled.
--- target/riscv/tcg/tcg-cpu.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
target/riscv/tcg/tcg-cpu.c +7 -7
@@ -1339,16 +1339,16 @@ static void cpu_set_profile(Object *obj, Visitor *v, const char *name,if (profile->enabled) { cpu->env.priv_ver = profile->priv_spec; - }#ifndef CONFIG_USER_ONLY -if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { -object_property_set_bool (obj,"mmu" , true,NULL ); -const char *satp_prop =satp_mode_str (profile->satp_mode, -riscv_cpu_is_32bit (cpu)); -object_property_set_bool (obj, satp_prop, profile->enabled,NULL ); - } +if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { +object_property_set_bool (obj,"mmu" , true,NULL ); +const char *satp_prop =satp_mode_str (profile->satp_mode, +riscv_cpu_is_32bit (cpu)); +object_property_set_bool (obj, satp_prop, true,NULL ); + }#endif + }for (i =0 ; misa_bits[i] !=0 ; i++) {uint32_t bit = misa_bits[i];
Signature · 1 line
2.49.0
PATCH v2 1/3 target/riscv/cpu.c: add 'sdtrig' in riscv,isa
In reply to Daniel Henrique BarbozaWe have support for sdtrig for awhile but we are not advertising it. It is enabled by default via the 'debug' flag. Use the same flag to also advertise sdtrig.
Add an exception in disable_priv_spec_isa_exts() to avoid spamming warnings for 'sdtrig' for vendor CPUs like sifive_u.
--- target/riscv/cpu.c | 1 + target/riscv/tcg/tcg-cpu.c | 9 +++++++++ tests/data/acpi/riscv64/virt/RHCT | Bin 400 -> 406 bytes 3 files changed, 10 insertions(+)
target/riscv/cpu.c +1 -0
@@ -189,6 +189,7 @@ const RISCVIsaExtData isa_edata_arr[] = {ISA_EXT_DATA_ENTRY (zvkt,PRIV_VERSION_1_12_0 , ext_zvkt),ISA_EXT_DATA_ENTRY (zhinx,PRIV_VERSION_1_12_0 , ext_zhinx),ISA_EXT_DATA_ENTRY (zhinxmin,PRIV_VERSION_1_12_0 , ext_zhinxmin), +ISA_EXT_DATA_ENTRY (sdtrig,PRIV_VERSION_1_12_0 , debug),ISA_EXT_DATA_ENTRY (shcounterenw,PRIV_VERSION_1_12_0 , has_priv_1_12),ISA_EXT_DATA_ENTRY (sha,PRIV_VERSION_1_12_0 , ext_sha), ISA_EXT_DATA_ENTRY(shgatpa, PRIV_VERSION_1_12_0, has_priv_1_12),
target/riscv/tcg/tcg-cpu.c +9 -0
@@ -451,6 +451,15 @@ static void riscv_cpu_disable_priv_spec_isa_exts(RISCVCPU *cpu)continue ; } +/* +* cpu.debug = true is marked as 'sdtrig', priv spec 1.12. +* Skip this warning dince existing CPUs with older priv +* specd and debug = true will be impacted. +*/ +if (!strcmp (edata->name,"sdtrig" )) { +continue ; + } +isa_ext_update_enabled (cpu, edata->ext_enable_offset, false);/*
tests/data/acpi/riscv64/virt/RHCT binary +0 -0
Signature · 1 line
2.49.0
PATCH v2 2/3 target/riscv/cpu.c: add 'ssstrict' to riscv,isa
In reply to Daniel Henrique Barboza'ssstrict' is a RVA23 profile-defined extension defined as follows:
"No non-conforming extensions are present. Attempts to execute unimplemented opcodes or access unimplemented CSRs in the standard or reserved encoding spaces raises an illegal instruction exception that results in a contained trap to the supervisor-mode trap handler."
In short, we need to throw an exception when accessing unimplemented CSRs or opcodes. We do that, so let's advertise it.
Message-ID: <[email protected]>
--- target/riscv/cpu.c | 1 + tests/data/acpi/riscv64/virt/RHCT | Bin 406 -> 416 bytes 2 files changed, 1 insertion(+)
target/riscv/cpu.c +1 -0
@@ -217,6 +217,7 @@ const RISCVIsaExtData isa_edata_arr[] = {ISA_EXT_DATA_ENTRY (ssnpm,PRIV_VERSION_1_13_0 , ext_ssnpm),ISA_EXT_DATA_ENTRY (sspm,PRIV_VERSION_1_13_0 , ext_sspm),ISA_EXT_DATA_ENTRY (ssstateen,PRIV_VERSION_1_12_0 , ext_ssstateen), +ISA_EXT_DATA_ENTRY (ssstrict,PRIV_VERSION_1_12_0 , has_priv_1_12),ISA_EXT_DATA_ENTRY (sstc,PRIV_VERSION_1_12_0 , ext_sstc),ISA_EXT_DATA_ENTRY (sstvala,PRIV_VERSION_1_12_0 , has_priv_1_12), ISA_EXT_DATA_ENTRY(sstvecd, PRIV_VERSION_1_12_0, has_priv_1_12),
tests/data/acpi/riscv64/virt/RHCT binary +0 -0
Signature · 1 line
2.49.0
PATCH v2 2/3 target/riscv/tcg: decouple profile enablement from user prop
In reply to Daniel Henrique BarbozaWe have code in riscv_cpu_add_profiles() to enable a profile right away in case a CPU chose the profile during its cpu_init(). But we're using the user callback option to do so, setting profile->user_set.
Create a new helper that does all the grunt work to enable/disable a given profile. Use this new helper in the cases where we want a CPU to be compatible to a certain profile, leaving the user callback to be used exclusively by users.
--- target/riscv/tcg/tcg-cpu.c | 127 +++++++++++++++++++------------------ 1 file changed, 67 insertions(+), 60 deletions(-)
target/riscv/tcg/tcg-cpu.c +67 -60
@@ -1140,6 +1140,70 @@ static bool riscv_cpu_is_generic(Object *cpu_obj)return object_dynamic_cast (cpu_obj,TYPE_RISCV_DYNAMIC_CPU ) !=NULL ; } +static void riscv_cpu_set_profile (RISCVCPU *cpu, +RISCVCPUProfile *profile, +bool enabled) +{ +int i, ext_offset; + +if (profile->u_parent !=NULL ) { +riscv_cpu_set_profile (cpu, profile->u_parent, enabled); + } + +if (profile->s_parent !=NULL ) { +riscv_cpu_set_profile (cpu, profile->s_parent, enabled); + } + + profile->enabled = enabled; + +if (profile->enabled) { + cpu->env.priv_ver = profile->priv_spec; + +#ifndef CONFIG_USER_ONLY +if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { +object_property_set_bool (OBJECT (cpu),"mmu" , true,NULL ); +const char *satp_prop =satp_mode_str (profile->satp_mode, +riscv_cpu_is_32bit (cpu)); +object_property_set_bool (OBJECT (cpu), satp_prop, true,NULL ); + } +#endif + } + +for (i =0 ; misa_bits[i] !=0 ; i++) { +uint32_t bit = misa_bits[i]; + +if (!(profile->misa_ext & bit)) { +continue ; + } + +if (bit ==RVI && !profile->enabled) { +/* +* Disabling profiles will not disable the base +* ISA RV64I. +*/ +continue ; + } + +cpu_misa_ext_add_user_opt (bit, profile->enabled); +riscv_cpu_write_misa_bit (cpu, bit, profile->enabled); + } + +for (i =0 ; profile->ext_offsets[i] !=RISCV_PROFILE_EXT_LIST_END ; i++) { + ext_offset = profile->ext_offsets[i]; + +if (profile->enabled) { +if (cpu_cfg_offset_is_named_feat (ext_offset)) { +riscv_cpu_enable_named_feat (cpu, ext_offset); + } + +cpu_bump_multi_ext_priv_ver (&cpu->env, ext_offset); + } + +cpu_cfg_ext_add_user_opt (ext_offset, profile->enabled); +isa_ext_update_enabled (cpu, ext_offset, profile->enabled); + } +} +/* * We'll get here via the following path: *
@@ -1306,7 +1370,6 @@ static void cpu_set_profile(Object *obj, Visitor *v, const char *name,RISCVCPUProfile *profile = opaque;RISCVCPU *cpu =RISCV_CPU (obj);bool value; -int i, ext_offset;if (riscv_cpu_is_vendor (obj)) { error_setg(errp, "Profile %s is not available for vendor CPUs",
@@ -1325,64 +1388,8 @@ static void cpu_set_profile(Object *obj, Visitor *v, const char *name, } profile->user_set = true; - profile->enabled = value; - -if (profile->u_parent !=NULL ) { -object_property_set_bool (obj, profile->u_parent->name, - profile->enabled,NULL ); - } - -if (profile->s_parent !=NULL ) { -object_property_set_bool (obj, profile->s_parent->name, - profile->enabled,NULL ); - } - -if (profile->enabled) { - cpu->env.priv_ver = profile->priv_spec; - -#ifndef CONFIG_USER_ONLY -if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { -object_property_set_bool (obj,"mmu" , true,NULL ); -const char *satp_prop =satp_mode_str (profile->satp_mode, -riscv_cpu_is_32bit (cpu)); -object_property_set_bool (obj, satp_prop, true,NULL ); - } -#endif - } - -for (i =0 ; misa_bits[i] !=0 ; i++) { -uint32_t bit = misa_bits[i]; - -if (!(profile->misa_ext & bit)) { -continue ; - } -if (bit ==RVI && !profile->enabled) { -/* -* Disabling profiles will not disable the base -* ISA RV64I. -*/ -continue ; - } - -cpu_misa_ext_add_user_opt (bit, profile->enabled); -riscv_cpu_write_misa_bit (cpu, bit, profile->enabled); - } - -for (i =0 ; profile->ext_offsets[i] !=RISCV_PROFILE_EXT_LIST_END ; i++) { - ext_offset = profile->ext_offsets[i]; - -if (profile->enabled) { -if (cpu_cfg_offset_is_named_feat (ext_offset)) { -riscv_cpu_enable_named_feat (cpu, ext_offset); - } - -cpu_bump_multi_ext_priv_ver (&cpu->env, ext_offset); - } - -cpu_cfg_ext_add_user_opt (ext_offset, profile->enabled); -isa_ext_update_enabled (cpu, ext_offset, profile->enabled); - } +riscv_cpu_set_profile (cpu, profile, value); } static void cpu_get_profile(Object *obj, Visitor *v, const char *name,
@@ -1397,7 +1404,7 @@ static void cpu_get_profile(Object *obj, Visitor *v, const char *name,static void riscv_cpu_add_profiles (Object *cpu_obj) {for (int i =0 ; riscv_profiles[i] !=NULL ; i++) { -const RISCVCPUProfile *profile = riscv_profiles[i]; +RISCVCPUProfile *profile = riscv_profiles[i]; object_property_add(cpu_obj, profile->name, "bool", cpu_get_profile, cpu_set_profile,
@@ -1409,7 +1416,7 @@ static void riscv_cpu_add_profiles(Object *cpu_obj)* case. */ if (profile->enabled) { -object_property_set_bool (cpu_obj, profile->name, true,NULL ); +riscv_cpu_set_profile (RISCV_CPU (cpu_obj), profile, true); } } }
Signature · 1 line
2.49.0
Re: [PATCH v2 2/3] target/riscv/tcg: decouple profile enablement from user prop
Quoted 10 lines · Daniel Henrique Barboza
We have code in
riscv_cpu_add_profiles()to enable a profile right away in case a CPU chose the profile during itscpu_init(). But we're using the user callback option to do so, settingprofile->user_set.Create a new helper that does all the grunt work to enable/disable a given profile. Use this new helper in the cases where we want a CPU to be compatible to a certain profile, leaving the user callback to be used exclusively by users.
Quoted 5 lines
Fixes fba92a92e3 ("target/riscv: add 'rva22u64' CPU")Signed-off-by Daniel Henrique Barboza <[email protected]>Reviewed-by Andrew Jones <[email protected]>Reviewed-by Björn Töpel <[email protected]>Tested-by Björn Töpel <[email protected]>
Alistair
Quoted 175 lines
--- target/riscv/tcg/tcg-cpu.c | 127 +++++++++++++++++++------------------ 1 file changed, 67 insertions(+), 60 deletions(-)target/riscv/tcg/tcg-cpu.c +67
-61@@ -1140,6 +1140,70 @@ static bool riscv_cpu_is_generic(Object *cpu_obj)return object_dynamic_cast (cpu_obj,TYPE_RISCV_DYNAMIC_CPU ) !=NULL ; } +static void riscv_cpu_set_profile (RISCVCPU *cpu, +RISCVCPUProfile *profile, +bool enabled) +{ +int i, ext_offset; + +if (profile->u_parent !=NULL ) { +riscv_cpu_set_profile (cpu, profile->u_parent, enabled); + } + +if (profile->s_parent !=NULL ) { +riscv_cpu_set_profile (cpu, profile->s_parent, enabled); + } + + profile->enabled = enabled; + +if (profile->enabled) { + cpu->env.priv_ver = profile->priv_spec; + +#ifndef CONFIG_USER_ONLY +if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { +object_property_set_bool (OBJECT (cpu),"mmu" , true,NULL ); +const char *satp_prop =satp_mode_str (profile->satp_mode, +riscv_cpu_is_32bit (cpu)); +object_property_set_bool (OBJECT (cpu), satp_prop, true,NULL ); + } +#endif + } + +for (i =0 ; misa_bits[i] !=0 ; i++) { +uint32_t bit = misa_bits[i]; + +if (!(profile->misa_ext & bit)) { +continue ; + } + +if (bit ==RVI && !profile->enabled) { +/* +* Disabling profiles will not disable the base +* ISA RV64I. +*/ +continue ; + } + +cpu_misa_ext_add_user_opt (bit, profile->enabled); +riscv_cpu_write_misa_bit (cpu, bit, profile->enabled); + } + +for (i =0 ; profile->ext_offsets[i] !=RISCV_PROFILE_EXT_LIST_END ; i++) { + ext_offset = profile->ext_offsets[i]; + +if (profile->enabled) { +if (cpu_cfg_offset_is_named_feat (ext_offset)) { +riscv_cpu_enable_named_feat (cpu, ext_offset); + } + +cpu_bump_multi_ext_priv_ver (&cpu->env, ext_offset); + } + +cpu_cfg_ext_add_user_opt (ext_offset, profile->enabled); +isa_ext_update_enabled (cpu, ext_offset, profile->enabled); + } +} +/* * We'll get here via the following path: * @@ -1306,7 +1370,6 @@ static void cpu_set_profile(Object *obj, Visitor *v, const char *name,RISCVCPUProfile *profile = opaque;RISCVCPU *cpu =RISCV_CPU (obj);bool value; -int i, ext_offset;if (riscv_cpu_is_vendor (obj)) { error_setg(errp, "Profile %s is not available for vendor CPUs",@@ -1325,64 +1388,8 @@ static void cpu_set_profile(Object *obj, Visitor *v, const char *name, } profile->user_set = true; - profile->enabled = value; - -if (profile->u_parent !=NULL ) { -object_property_set_bool (obj, profile->u_parent->name, - profile->enabled,NULL ); - } - -if (profile->s_parent !=NULL ) { -object_property_set_bool (obj, profile->s_parent->name, - profile->enabled,NULL ); - } - -if (profile->enabled) { - cpu->env.priv_ver = profile->priv_spec; - -#ifndef CONFIG_USER_ONLY -if (profile->satp_mode !=RISCV_PROFILE_ATTR_UNUSED ) { -object_property_set_bool (obj,"mmu" , true,NULL ); -const char *satp_prop =satp_mode_str (profile->satp_mode, -riscv_cpu_is_32bit (cpu)); -object_property_set_bool (obj, satp_prop, true,NULL ); - } -#endif - } - -for (i =0 ; misa_bits[i] !=0 ; i++) { -uint32_t bit = misa_bits[i]; - -if (!(profile->misa_ext & bit)) { -continue ; - } -if (bit ==RVI && !profile->enabled) { -/* -* Disabling profiles will not disable the base -* ISA RV64I. -*/ -continue ; - } - -cpu_misa_ext_add_user_opt (bit, profile->enabled); -riscv_cpu_write_misa_bit (cpu, bit, profile->enabled); - } - -for (i =0 ; profile->ext_offsets[i] !=RISCV_PROFILE_EXT_LIST_END ; i++) { - ext_offset = profile->ext_offsets[i]; - -if (profile->enabled) { -if (cpu_cfg_offset_is_named_feat (ext_offset)) { -riscv_cpu_enable_named_feat (cpu, ext_offset); - } - -cpu_bump_multi_ext_priv_ver (&cpu->env, ext_offset); - } - -cpu_cfg_ext_add_user_opt (ext_offset, profile->enabled); -isa_ext_update_enabled (cpu, ext_offset, profile->enabled); - } +riscv_cpu_set_profile (cpu, profile, value); } static void cpu_get_profile(Object *obj, Visitor *v, const char *name,@@ -1397,7 +1404,7 @@ static void cpu_get_profile(Object *obj, Visitor *v, const char *name,static void riscv_cpu_add_profiles (Object *cpu_obj) {for (int i =0 ; riscv_profiles[i] !=NULL ; i++) { -const RISCVCPUProfile *profile = riscv_profiles[i]; +RISCVCPUProfile *profile = riscv_profiles[i]; object_property_add(cpu_obj, profile->name, "bool", cpu_get_profile, cpu_set_profile,@@ -1409,7 +1416,7 @@ static void riscv_cpu_add_profiles(Object *cpu_obj)* case. */ if (profile->enabled) { -object_property_set_bool (cpu_obj, profile->name, true,NULL ); +riscv_cpu_set_profile (RISCV_CPU (cpu_obj), profile, true); } } } --2.49.0
PATCH v2 3/3 target/riscv/cpu.c: do better with 'named features' doc
In reply to Daniel Henrique BarbozaMost of the named features are added directly in isa_edata_arr[], some of them are also added in riscv_cpu_named_features(). There is a reason for that, and the existing docs can do better explaining it.
Message-ID: <[email protected]>
--- target/riscv/cpu.c | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)
target/riscv/cpu.c +12 -2
@@ -1378,13 +1378,23 @@ const RISCVCPUMultiExtConfig riscv_cpu_experimental_exts[] = {* 'Named features' is the name we give to extensions that we * don't want to expose to users. They are either immutable * (always enabled/disable) or they'll vary depending on -* the resulting CPU state. They have riscv,isa strings -* and priv_ver like regular extensions. +* the resulting CPU state. +* +* Some of them are always enabled depending on priv version +* of the CPU and are declared directly in isa_edata_arr[]. +* The ones listed here have special checks during finalize() +* time and require their own flags like regular extensions. +* See riscv_cpu_update_named_features() for more info. */ const RISCVCPUMultiExtConfig riscv_cpu_named_features[] = {MULTI_EXT_CFG_BOOL ("zic64b" , ext_zic64b, true),MULTI_EXT_CFG_BOOL ("ssstateen" , ext_ssstateen, true),MULTI_EXT_CFG_BOOL ("sha" , ext_sha, true), + +/* +* 'ziccrse' has its own flag because the KVM driver +* wants to enable/disable it on its own accord. +*/ MULTI_EXT_CFG_BOOL ("ziccrse" , ext_ziccrse, true), { },
Signature · 1 line
2.49.0
PATCH v2 3/3 target/riscv: add profile->present flag
In reply to Daniel Henrique BarbozaBjörn reported in [1] a case where a rv64 CPU is going through the profile code path to enable satp mode. In this case,the amount of extensions on top of the rv64 CPU made it compliant with the RVA22S64 profile during the validation of CPU 0. When the subsequent CPUs were initialized the static profile object has the 'enable' flag set, enabling the profile code path for those CPUs.
This happens because we are initializing and realizing each CPU before going to the next, i.e. init and realize CPU0, then init and realize CPU1 and so on. If we change any persistent state during the validation of CPU N it will interfere with the init/realization of CPU N+1.
We're using the 'enabled' profile flag to do two distinct things: inform cpu_init() that we want profile extensions to be enabled, and telling QMP that a profile is currently enabled in the CPU. We want to be flexible enough to recognize profile support for all CPUs that has the extension prerequisites, but we do not want to force the profile code path if a profile wasn't set too.
Add a new 'present' flag for profiles that will coexist with the 'enabled' flag. Enabling a profile means "we want to switch on all its mandatory extensions". A profile is 'present' if we asserted during validation that the CPU has the needed prerequisites.
This means that the case reported by Björn now results in RVA22S64.enabled=false and RVA22S64.present=true. QMP will recognize it as a RVA22 compliant CPU and we won't force the CPU into the profile path.
[1] https://lore.kernel.org/qemu-riscv/[email protected]/
--- target/riscv/cpu.h | 15 +++++++++++++++ target/riscv/riscv-qmp-cmds.c | 2 +- target/riscv/tcg/tcg-cpu.c | 11 +++-------- 3 files changed, 19 insertions(+), 9 deletions(-)
target/riscv/cpu.h +15 -0
@@ -82,7 +82,22 @@ typedef struct riscv_cpu_profile {struct riscv_cpu_profile *s_parent;const char *name;uint32_t misa_ext; +/* +* The profile is enabled/disabled via command line or +* via cpu_init(). Enabling a profile will add all its +* mandatory extensions in the CPU during init(). +*/ bool enabled; +/* +* The profile is present in the CPU, i.e. the current set of +* CPU extensions complies with it. A profile can be enabled +* and not present (e.g. the user disabled a mandatory extension) +* and the other way around (e.g. all mandatory extensions are +* present in a non-profile CPU). +* +* QMP uses this flag. +*/ +bool present;bool user_set;int priv_spec;int satp_mode;
target/riscv/riscv-qmp-cmds.c +1 -1
@@ -121,7 +121,7 @@ static void riscv_obj_add_profiles_qdict(Object *obj, QDict *qdict_out)for (int i =0 ; riscv_profiles[i] !=NULL ; i++) { profile = riscv_profiles[i]; - value =QOBJECT (qbool_from_bool (profile->enabled)); + value =QOBJECT (qbool_from_bool (profile->present));qdict_put_obj (qdict_out, profile->name, value); }
target/riscv/tcg/tcg-cpu.c +3 -8
@@ -841,16 +841,11 @@ static void riscv_cpu_check_parent_profile(RISCVCPU *cpu, RISCVCPUProfile *profile, RISCVCPUProfile *parent) { -const char *parent_name; -bool parent_enabled; - -if (!profile->enabled || !parent) { +if (!profile->present || !parent) {return ; } - parent_name = parent->name; - parent_enabled =object_property_get_bool (OBJECT (cpu), parent_name,NULL ); - profile->enabled = parent_enabled; + profile->present = parent->present; } static void riscv_cpu_validate_profile(RISCVCPU *cpu,
@@ -911,7 +906,7 @@ static void riscv_cpu_validate_profile(RISCVCPU *cpu, } } - profile->enabled = profile_impl; + profile->present = profile_impl;riscv_cpu_check_parent_profile (cpu, profile, profile->u_parent);riscv_cpu_check_parent_profile (cpu, profile, profile->s_parent);
Signature · 1 line
2.49.0
Please disregard this post - some old patches were left in the dir when I pressed "send" ...
Thanks,
Daniel
Quoted 32 lines · Daniel Henrique Barboza
Hi,
In this version I fixed the problems caused in bios-table-test qtest by patches 1 and 2.
A small change was also made in patch 1 to avoid spamming "Disabling sdtrig due to priv spec version" warnings when running vendor CPUs with priv spec < 1.12.
Patches based on alistair/riscv-to-apply.next.
Changes from v1:
- patch 1:
- skip the warning and disable of 'sdtrig' for CPUs that have privversion < 1.12- update bios-table-test
- patch 2:
- update bios-table-test
- v1 link: https://lore.kernel.org/qemu-riscv/[email protected]/Daniel Henrique Barboza (3):
target/riscv/cpu.c: add 'sdtrig' in riscv,isatarget/riscv/cpu.c: add 'ssstrict' to riscv,isatarget/riscv/cpu.c: do better with 'named features' doctarget/riscv/cpu.c | 16 ++++++++++++++-- target/riscv/tcg/tcg-cpu.c | 9 +++++++++ tests/data/acpi/riscv64/virt/RHCT | Bin 400 -> 416 bytes 3 files changed, 23 insertions(+), 2 deletions(-)