@@ -23,21 +23,23 @@ the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1
23
23
ARCH_FEATURES mechanism before calling it.
24
24
25
25
PV_TIME_FEATURES
26
- ============= ======== ==========
26
+
27
+ ============= ======== =================================================
27
28
Function ID: (uint32) 0xC5000020
28
29
PV_call_id: (uint32) The function to query for support.
29
30
Currently only PV_TIME_ST is supported.
30
31
Return value: (int64) NOT_SUPPORTED (-1) or SUCCESS (0) if the relevant
31
32
PV-time feature is supported by the hypervisor.
32
- ============= ======== ==========
33
+ ============= ======== =================================================
33
34
34
35
PV_TIME_ST
35
- ============= ======== ==========
36
+
37
+ ============= ======== ==============================================
36
38
Function ID: (uint32) 0xC5000021
37
39
Return value: (int64) IPA of the stolen time data structure for this
38
40
VCPU. On failure:
39
41
NOT_SUPPORTED (-1)
40
- ============= ======== ==========
42
+ ============= ======== ==============================================
41
43
42
44
The IPA returned by PV_TIME_ST should be mapped by the guest as normal memory
43
45
with inner and outer write back caching attributes, in the inner shareable
@@ -76,5 +78,5 @@ It is advisable that one or more 64k pages are set aside for the purpose of
76
78
these structures and not used for other purposes, this enables the guest to map
77
79
the region using 64k pages and avoids conflicting attributes with other memory.
78
80
79
- For the user space interface see Documentation/virt/kvm/devices/vcpu.rst
80
- section "3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL" .
81
+ For the user space interface see
82
+ :ref: ` Documentation/virt/kvm/devices/vcpu.rst < kvm_arm_vcpu_pvtime_ctrl >` .
0 commit comments