[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v1 RFC Zisslpcfi 3/9] target/riscv: implements CSRs and new b
Re: [PATCH v1 RFC Zisslpcfi 3/9] target/riscv: implements CSRs and new bits in existing CSRs in zisslpcfi
Wed, 15 Feb 2023 16:43:58 -1000
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
On 2/15/23 15:38, Deepak Gupta wrote:
I'll basically need two bits (one for forward cfi and one for backward cfi).
Are they separately enabled? It may also be possible to use a single bit and then perform
a runtime check. I guess I should read the spec...
But I need to throw away the TB if cfi enabling bits mismatch at the
time TB was generated and the current state of enabling bits.
Reason being, this needs to get translated again and zimops need to be
What's the best way to throw away a single TB?
You don't throw TBs away at all.
The current cpu state is produced by cpu_get_tb_cpu_state. This is included into the hash
table lookup and will only match a TB which has been generated with the same state. Which
means that you can have multiple live TBs, those with CFI enabled and those without, and
the correct one will be selected at runtime.