On 8/17/24 08:58, Carl Hauser wrote:
Yes, but ...
isn't the state of dc->fsr_qne at translation time irrelevant?
No, because patch 4 made it part of the hashed TB state.
It's checked and verified, generating a new TB if state does not match.
And changing it at
translation time (line 4593) is dangerous (because it pertains to runtime, not translation
time); i.e. why is 0 stored at both translation time (4593) and at runtime (4591)?
That keeps the translation time state in sync with the runtime state until the
end of the TB.
r~
