You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec states, "The hypervisor should copy the value written to senvcfg.PMM by the guest to the hstatus.HUPMM field prior to invoking HLV.* or HSV.* instructions in U-mode."
Is this a mandatory requirement, or just a recommendation? If it is mandatory, then senvcfg.PMM and hstatus.HUPMM would always be equal. Why does VU mode access for HLV* and HSV.* in U mode require adding the hstatus.HUPMM field, but VS mode access for these instructions in U mode can directly use the henvcfg.PMM setting?
The text was updated successfully, but these errors were encountered:
sealman-Kuo
changed the title
Some questions about hstatus.HUPMM
Questions about hstatus.HUPMM
Aug 21, 2024
This is only a recommendation how software may manage these registers. A hypervisor is free to ignore this recommendation, but it is unclear how HLV.* and HSV.* instructions would be used in this case.
Hi, I have some questions about hstatus.HUPMM.
The spec states, "The hypervisor should copy the value written to senvcfg.PMM by the guest to the hstatus.HUPMM field prior to invoking HLV.* or HSV.* instructions in U-mode."
Is this a mandatory requirement, or just a recommendation? If it is mandatory, then senvcfg.PMM and hstatus.HUPMM would always be equal. Why does VU mode access for HLV* and HSV.* in U mode require adding the hstatus.HUPMM field, but VS mode access for these instructions in U mode can directly use the henvcfg.PMM setting?
The text was updated successfully, but these errors were encountered: