diff options
| author | Daniel Henrique Barboza <dbarboza@ventanamicro.com> | 2025-05-28 15:44:06 -0300 |
|---|---|---|
| committer | Alistair Francis <alistair.francis@wdc.com> | 2025-07-04 21:09:48 +1000 |
| commit | f655704c3dfefd57172e3347c22aca18283ee2b7 (patch) | |
| tree | 56ff080337fd33a383325e5e26e6fb9b895f8c80 /scripts/tracetool/backend/log.py | |
| parent | a429f9304d54e9a44773b753d0844204b4b3b22f (diff) | |
| download | qemu-f655704c3dfefd57172e3347c22aca18283ee2b7.zip qemu-f655704c3dfefd57172e3347c22aca18283ee2b7.tar.gz qemu-f655704c3dfefd57172e3347c22aca18283ee2b7.tar.bz2 | |
target/riscv/tcg: decouple profile enablement from user prop
We 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.
Fixes: fba92a92e3 ("target/riscv: add 'rva22u64' CPU")
Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
Tested-by: Björn Töpel <bjorn@rivosinc.com>
Message-ID: <20250528184407.1451983-3-dbarboza@ventanamicro.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'scripts/tracetool/backend/log.py')
0 files changed, 0 insertions, 0 deletions