target/riscv/cpu.c: fix Zvkb extension config
This code has a typo that writes zvkb to zvkg, causing users can't enable zvkb through the config. This patch gets this fixed. Signed-off-by: Yangyu Chen <cyy@cyyself.name> Fixes: ea61ef7097d0 ("target/riscv: Move vector crypto extensions to riscv_cpu_extensions") Reviewed-by: LIU Zhiwei <zhiwei_liu@linux.alibaba.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Reviewed-by: Max Chou <max.chou@sifive.com> Reviewed-by: Weiwei Li <liwei1518@gmail.com> Message-ID: <tencent_7E34EEF0F90B9A68BF38BEE09EC6D4877C0A@qq.com> Cc: qemu-stable <qemu-stable@nongnu.org> Signed-off-by: Alistair Francis <alistair.francis@wdc.com> (cherry picked from commit ff33b7a9699e977a050a1014c617a89da1bf8295) Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
This commit is contained in:
parent
ec182b1045
commit
4cba687b86
@ -1359,7 +1359,7 @@ const RISCVCPUMultiExtConfig riscv_cpu_extensions[] = {
|
||||
/* Vector cryptography extensions */
|
||||
MULTI_EXT_CFG_BOOL("zvbb", ext_zvbb, false),
|
||||
MULTI_EXT_CFG_BOOL("zvbc", ext_zvbc, false),
|
||||
MULTI_EXT_CFG_BOOL("zvkb", ext_zvkg, false),
|
||||
MULTI_EXT_CFG_BOOL("zvkb", ext_zvkb, false),
|
||||
MULTI_EXT_CFG_BOOL("zvkg", ext_zvkg, false),
|
||||
MULTI_EXT_CFG_BOOL("zvkned", ext_zvkned, false),
|
||||
MULTI_EXT_CFG_BOOL("zvknha", ext_zvknha, false),
|
||||
|
Loading…
x
Reference in New Issue
Block a user