Skip to content
Snippets Groups Projects
Commit 389b2e70 authored by Max Chou's avatar Max Chou Committed by Alistair Francis
Browse files

target/riscv: Add cfg property for Zvkb extension


After vector crypto spec v1.0.0-rc3 release, the Zvkb extension is
defined as a proper subset of the Zvbb extension. And both the Zvkn and
Zvks shorthand extensions replace the included Zvbb extension by Zvkb
extnesion.

Signed-off-by: default avatarMax Chou <max.chou@sifive.com>
Acked-by: default avatarAlistair Francis <alistair.francis@wdc.com>
Reviewed-by: default avatarDaniel Henrique Barboza <dbarboza@ventanamicro.com>
Message-ID: <20231026151828.754279-4-max.chou@sifive.com>
Signed-off-by: default avatarAlistair Francis <alistair.francis@wdc.com>
parent 1c32b630
No related branches found
No related tags found
No related merge requests found
...@@ -90,6 +90,7 @@ struct RISCVCPUConfig { ...@@ -90,6 +90,7 @@ struct RISCVCPUConfig {
bool ext_zve64d; bool ext_zve64d;
bool ext_zvbb; bool ext_zvbb;
bool ext_zvbc; bool ext_zvbc;
bool ext_zvkb;
bool ext_zvkg; bool ext_zvkg;
bool ext_zvkned; bool ext_zvkned;
bool ext_zvknha; bool ext_zvknha;
......
...@@ -508,9 +508,9 @@ void riscv_cpu_validate_set_extensions(RISCVCPU *cpu, Error **errp) ...@@ -508,9 +508,9 @@ void riscv_cpu_validate_set_extensions(RISCVCPU *cpu, Error **errp)
* In principle Zve*x would also suffice here, were they supported * In principle Zve*x would also suffice here, were they supported
* in qemu * in qemu
*/ */
if ((cpu->cfg.ext_zvbb || cpu->cfg.ext_zvkg || cpu->cfg.ext_zvkned || if ((cpu->cfg.ext_zvbb || cpu->cfg.ext_zvkb || cpu->cfg.ext_zvkg ||
cpu->cfg.ext_zvknha || cpu->cfg.ext_zvksed || cpu->cfg.ext_zvksh) && cpu->cfg.ext_zvkned || cpu->cfg.ext_zvknha || cpu->cfg.ext_zvksed ||
!cpu->cfg.ext_zve32f) { cpu->cfg.ext_zvksh) && !cpu->cfg.ext_zve32f) {
error_setg(errp, error_setg(errp,
"Vector crypto extensions require V or Zve* extensions"); "Vector crypto extensions require V or Zve* extensions");
return; return;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment