[mmu shared tlb] index of a set seems to be extracted from VPN0 even in the case of superpage ?

[khandelwaltanuj]

Hello,

I have a question regarding how an index of a set is calculated in the case of a superpage. It seems to use the bits [$clog2(SharedTlbDepth) -1: 0] of VPN. I am thinking in the case of a superpage, vpn0 is a dont care and we may get wrong miss or data if PTE was overwritten in the meantime ?

For example in the following case of SV39 5045e9fed8 vpn = {141, 2F, 9f} => index = 1F (its a miss) data A is written in the SRAM @set 1F 5045f029e8 vpn = {141, 2F, 102} => index = 2 (its a miss) data B(PTE is overwritten) is written in the SRAM @set 02 5045f5fd60 vpn = {141 2F, 15F} => index = 1F (its a hit) data A reseived from the SRAM from set 1F

It do not seems to be the correcte data.

Thanks and Regards Tanuj Khandelwal

[khandelwaltanuj]

Keeping a trace of the test failing:

python3 $CVA6_REPO_DIR/verif/core-v-verif/lib/cv_dv_utils/python/sim_cmd/run_test.py --yaml sim_questa.yaml --test_name test_random_in_pmpaddr_region --debug UVM_DEBUG --seed 288576037

[khandelwaltanuj]

Hi @AngelaGonzalezMarino @cfuguet

Any comment on this ?

Thanks a lot Tanuj

[github-actions[bot]]

👋 Hi there!

This issue seems inactive. Need more help? Feel free to update us. If there are no updates within the next few days, we'll go ahead and close this issue. 😊

[khandelwaltanuj]

Hi @fatimasaleem

Is it possible for you to comment on this please ?

Thanks and regards Tanuj Khandelwal