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 virtualization section talks about virtualizing or emulating access to mconfigptr, but there is no concept of M-mode virtualization in the RV H extension. In a virtualized system, the guest only consists of S- and U-mode components (S mode running firmware and then OS). In a virtualized system, SBI is implemented by the hypervisor and no M-mode registers are modelled.
Thus I would either delete this section entirely or flatly state that UD does not concern with virtualization, e.g. a hypervisor would model the guest environment based on its view of the host envo, which it bases on DT/ACPI, not on UD data which it also cannot see.
The text was updated successfully, but these errors were encountered:
The virtualization section talks about virtualizing or emulating access to mconfigptr, but there is no concept of M-mode virtualization in the RV H extension. In a virtualized system, the guest only consists of S- and U-mode components (S mode running firmware and then OS). In a virtualized system, SBI is implemented by the hypervisor and no M-mode registers are modelled.
Thus I would either delete this section entirely or flatly state that UD does not concern with virtualization, e.g. a hypervisor would model the guest environment based on its view of the host envo, which it bases on DT/ACPI, not on UD data which it also cannot see.
The text was updated successfully, but these errors were encountered: