qemu-riscv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC 3/6] target/riscv: rvk: add flag support for Zk/Zkn/Zknd/Zknd/Z


From: liweiwei
Subject: Re: [RFC 3/6] target/riscv: rvk: add flag support for Zk/Zkn/Zknd/Zknd/Zkne/Zknh/Zks/Zksed/Zksh/Zkr
Date: Wed, 3 Nov 2021 15:22:51 +0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0


在 2021/11/3 上午9:21, Richard Henderson 写道:
On 11/2/21 9:06 PM, liweiwei wrote:

在 2021/11/3 上午1:56, Richard Henderson 写道:
On 11/1/21 11:11 PM, liweiwei wrote:
+        if (cpu->cfg.ext_zk) {
+            cpu->cfg.ext_zbkb = true;
+            cpu->cfg.ext_zbkc = true;
+            cpu->cfg.ext_zbkx = true;
+            cpu->cfg.ext_zknd = true;
+            cpu->cfg.ext_zkne = true;
+            cpu->cfg.ext_zknh = true;
+            cpu->cfg.ext_zkr = true;
+        }

Section 2.12 lists instead the larger Zkn, Zks, Zkt extensions.
I think it's better to follow that.

OK. I'll replace this with setting ext_zkn, ext_zks, ext_zkt true. By the way, Zkt only includes partial RVI/M/C instructions. Is it neccessary to distinguish them?

I don't know if Zkt needs to be called out; it probably depends on whether it is exposed to the guest via some MISA csr extension.
It seems not  exposed to the guest via some MISA csr extension. And it also doesn't define a set of instructions available in the core. It just restricts the set of instructions to have 'data-independent execution time'.


r~




reply via email to

[Prev in Thread] Current Thread [Next in Thread]