KVM: Add idempotent controls for migrating system counter state
Subsystems (7)
v4 cover KVM: Add idempotent controls for migrating system counter state
KVM's current means of saving/restoring system counters is plagued with temporal issues. At least on ARM64 and x86, we migrate the guest's system counter by-value through the respective guest system register values (cntvct_el0, ia32_tsc). Restoring system counters by-value is brittle as the state is not idempotent: the host system counter is still oscillating between the attempted save and restore. Furthermore, VMMs may wish to transparently live migrate guest VMs, meaning that they include the elapsed time due to live migration blackout in the guest system counter view. The VMM thread could be preempted for any number of reasons (scheduler, L0 hypervisor under nested) between the time that it calculates the desired guest counter value and when KVM actually sets this counter state.
Despite the value-based interface that we present to userspace, KVM actually has idempotent guest controls by way of system counter offsets. We can avoid all of the issues associated with a value-based interface by abstracting these offset controls in new ioctls. This series introduces new vCPU device attributes to provide userspace access to the vCPU's system counter offset.
Patch 1 adopts Paolo's suggestion, augmenting the KVM_{GET,SET}_CLOCK ioctls to provide userspace with a (host_tsc, realtime) instant. This is essential for a VMM to perform precise migration of the guest's system counters.
Patches 2-3 add support for x86 by shoehorning the new controls into the pre-existing synchronization heuristics.
Patches 4-5 implement a test for the new additions to KVM_{GET,SET}_CLOCK.
Patch 6 fixes some assertions in the kvm device attribute helpers.
Patches 7-8 implement at test for the tsc offset attribute introduced in patch 3.
Patch 9 adds a device attribute for the arm64 virtual counter-timer offset.
Patch 10 extends the test from patch 8 to cover the arm64 virtual counter-timer offset.
Patch 11 adds a device attribute for the arm64 physical counter-timer offset. Currently, this is implemented as a synthetic register, forcing the guest to trap to the host and emulating the offset in the fast exit path. Later down the line we will have hardware with FEAT_ECV, which allows the hypervisor to perform physical counter-timer offsetting in hardware (CNTPOFF_EL2).
Patch 12 extends the test from patch 8 to cover the arm64 physical counter-timer offset.
Patch 13 introduces a benchmark to measure the overhead of emulation in patch 11.
This series was tested on both an Ampere Mt. Jade and Haswell systems.
Physical counter benchmark
--------------------------
The following data was collected by running 10000 iterations of the benchmark test from Patch 6 on an Ampere Mt. Jade reference server, A 2S machine with 2 80-core Ampere Altra SoCs. Measurements were collected for both VHE and nVHE operation using the kvm-arm.mode= command-line parameter.
nVHE
----
+--------------------+--------+---------+ | Metric | Native | Trapped | +--------------------+--------+---------+ | Average | 54ns | 148ns | | Standard Deviation | 124ns | 122ns | | 95th Percentile | 258ns | 348ns | +--------------------+--------+---------+
VHE
---
+--------------------+--------+---------+ | Metric | Native | Trapped | +--------------------+--------+---------+ | Average | 53ns | 152ns | | Standard Deviation | 92ns | 94ns | | 95th Percentile | 204ns | 307ns | +--------------------+--------+---------+
This series applies cleanly to kvm/queue at the following commit:
8ad5e63649ff ("KVM: Don't take mmu_lock for range invalidation unless necessary")
v1 -> v2:
- Reimplemented as vCPU device attributes instead of a distinct ioctl.
- Added the (realtime, host_tsc) instant support to KVM_{GET,SET}_CLOCK
- Changed the arm64 implementation to broadcast counter offset values to all vCPUs in a guest. This upholds the architectural expectations of a consistent counter-timer across CPUs.
- Fixed a bug with traps in VHE mode. We now configure traps on every transition into a guest to handle differing VMs (trapped, emulated).
v2 -> v3:
- Added documentation for additions to KVM_{GET,SET}_CLOCK
- Added documentation for all new vCPU attributes
- Added documentation for suggested algorithm to migrate a guest's
TSC(s)
- Bug fixes throughout series
- Rename KVM_CLOCK_REAL_TIME -> KVM_CLOCK_REALTIME
v3 -> v4:
- Added patch to address incorrect device helper assertions (Drew)
- Carried Drew's r-b tags where appropriate
- x86 selftest cleanup
- Removed stale kvm_timer_init_vhe() function
- Removed unnecessary GUEST_DONE() from selftests
v1: https://lore.kernel.org/kvm/[email protected]/
v2: https://lore.kernel.org/r/[email protected]
v3: https://lore/kernel.org/r/[email protected]
Oliver Upton (13):
KVM: x86: Report host tsc and realtime values in KVM_GET_CLOCK
KVM: x86: Refactor tsc synchronization code
KVM: x86: Expose TSC offset controls to userspace
tools: arch: x86: pull in pvclock headers
selftests: KVM: Add test for KVM_{GET,SET}_CLOCK
selftests: KVM: Fix kvm device helper ioctl assertions
selftests: KVM: Add helpers for vCPU device attributes
selftests: KVM: Introduce system counter offset test
KVM: arm64: Allow userspace to configure a vCPU's virtual offset
selftests: KVM: Add support for aarch64 to system_counter_offset_test
KVM: arm64: Provide userspace access to the physical counter offset
selftests: KVM: Test physical counter offsetting
selftests: KVM: Add counter emulation benchmark
Documentation/virt/kvm/api.rst | 42 +- Documentation/virt/kvm/devices/vcpu.rst | 101 +++++ Documentation/virt/kvm/locking.rst | 11 + arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/include/asm/kvm_hyp.h | 2 - arch/arm64/include/asm/sysreg.h | 1 + arch/arm64/include/uapi/asm/kvm.h | 2 + arch/arm64/kvm/arch_timer.c | 140 ++++-- arch/arm64/kvm/arm.c | 4 +- arch/arm64/kvm/hyp/include/hyp/switch.h | 23 + arch/arm64/kvm/hyp/include/hyp/timer-sr.h | 26 ++ arch/arm64/kvm/hyp/nvhe/switch.c | 2 - arch/arm64/kvm/hyp/nvhe/timer-sr.c | 21 +- arch/arm64/kvm/hyp/vhe/timer-sr.c | 27 ++ arch/x86/include/asm/kvm_host.h | 4 + arch/x86/include/uapi/asm/kvm.h | 4 + arch/x86/kvm/x86.c | 422 ++++++++++++++---- include/kvm/arm_arch_timer.h | 2 - include/uapi/linux/kvm.h | 7 +- tools/arch/x86/include/asm/pvclock-abi.h | 48 ++ tools/arch/x86/include/asm/pvclock.h | 103 +++++ tools/testing/selftests/kvm/.gitignore | 3 + tools/testing/selftests/kvm/Makefile | 4 + .../kvm/aarch64/counter_emulation_benchmark.c | 215 +++++++++ .../selftests/kvm/include/aarch64/processor.h | 24 + .../testing/selftests/kvm/include/kvm_util.h | 11 + tools/testing/selftests/kvm/lib/kvm_util.c | 44 +- .../kvm/system_counter_offset_test.c | 206 +++++++++ .../selftests/kvm/x86_64/kvm_clock_test.c | 206 +++++++++ 29 files changed, 1548 insertions(+), 158 deletions(-) create mode 100644 arch/arm64/kvm/hyp/include/hyp/timer-sr.h create mode 100644 tools/arch/x86/include/asm/pvclock-abi.h create mode 100644 tools/arch/x86/include/asm/pvclock.h create mode 100644 tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c create mode 100644 tools/testing/selftests/kvm/system_counter_offset_test.c create mode 100644 tools/testing/selftests/kvm/x86_64/kvm_clock_test.c
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 1/13 KVM: x86: Report host tsc and realtime values in KVM_GET_CLOCK
Handling the migration of TSCs correctly is difficult, in part because Linux does not provide userspace with the ability to retrieve a (TSC, realtime) clock pair for a single instant in time. In lieu of a more convenient facility, KVM can report similar information in the kvm_clock structure.
Provide userspace with a host TSC & realtime pair iff the realtime clock is based on the TSC. If userspace provides KVM_SET_CLOCK with a valid realtime value, advance the KVM clock by the amount of elapsed time. Do not step the KVM clock backwards, though, as it is a monotonic oscillator.
--- Documentation/virt/kvm/api.rst | 42 +++++++-- arch/x86/include/asm/kvm_host.h | 3 + arch/x86/kvm/x86.c | 149 ++++++++++++++++++++------------ include/uapi/linux/kvm.h | 7 +- 4 files changed, 137 insertions(+), 64 deletions(-)
Documentation/virt/kvm/api.rst +33 -9
@@ -993,20 +993,34 @@ such as migration. When KVM_CAP_ADJUST_CLOCK is passed to KVM_CHECK_EXTENSION, it returns the set of bits that KVM can return in struct kvm_clock_data's flag member. -The only flag defined now is KVM_CLOCK_TSC_STABLE. If set, the returned -value is the exact kvmclock value seen by all VCPUs at the instant -when KVM_GET_CLOCK was called. If clear, the returned value is simply -CLOCK_MONOTONIC plus a constant offset; the offset can be modified -with KVM_SET_CLOCK. KVM will try to make all VCPUs follow this clock, -but the exact value read by each VCPU could differ, because the host -TSC is not stable. +FLAGS: + +KVM_CLOCK_TSC_STABLE. If set, the returned value is the exact kvmclock +value seen by all VCPUs at the instant when KVM_GET_CLOCK was called. +If clear, the returned value is simply CLOCK_MONOTONIC plus a constant +offset; the offset can be modified with KVM_SET_CLOCK. KVM will try +to make all VCPUs follow this clock, but the exact value read by each +VCPU could differ, because the host TSC is not stable. + +KVM_CLOCK_REALTIME. If set, the `realtime` field in the kvm_clock_data +structure is populated with the value of the host's real time +clocksource at the instant when KVM_GET_CLOCK was called. If clear, +the `realtime` field does not contain a value. + +KVM_CLOCK_HOST_TSC. If set, the `host_tsc` field in the kvm_clock_data +structure is populated with the value of the host's timestamp counter (TSC) +at the instant when KVM_GET_CLOCK was called. If clear, the `host_tsc` field +does not contain a value. :: struct kvm_clock_data { __u64 clock; /* kvmclock current value */ __u32 flags; - __u32 pad[9]; + __u32 pad0; + __u64 realtime; + __u64 host_tsc; + __u32 pad[4]; };
@@ -1023,12 +1037,22 @@ Sets the current timestamp of kvmclock to the value specified in its parameter. In conjunction with KVM_GET_CLOCK, it is used to ensure monotonicity on scenarios such as migration. +FLAGS: + +KVM_CLOCK_REALTIME. If set, KVM will compare the value of the `realtime` field +with the value of the host's real time clocksource at the instant when +KVM_SET_CLOCK was called. The difference in elapsed time is added to the final +kvmclock value that will be provided to guests. + :: struct kvm_clock_data { __u64 clock; /* kvmclock current value */ __u32 flags; - __u32 pad[9]; + __u32 pad0; + __u64 realtime; + __u64 host_tsc; + __u32 pad[4]; };
arch/x86/include/asm/kvm_host.h +3 -0
@@ -1932,4 +1932,7 @@ int kvm_cpu_dirty_log_size(void);int alloc_all_memslots_rmaps (struct kvm *kvm); +#define KVM_CLOCK_VALID_FLAGS \ + (KVM_CLOCK_TSC_STABLE | KVM_CLOCK_REALTIME | KVM_CLOCK_HOST_TSC) +#endif /* _ASM_X86_KVM_HOST_H */
arch/x86/kvm/x86.c +95 -54
200 lines not on this page · raw message
include/uapi/linux/kvm.h +6 -1
@@ -1223,11 +1223,16 @@ struct kvm_irqfd {/* Do not use 1, KVM_CHECK_EXTENSION returned it before we had flags. */ #define KVM_CLOCK_TSC_STABLE 2 +#define KVM_CLOCK_REALTIME (1 << 2) +#define KVM_CLOCK_HOST_TSC (1 << 3)struct kvm_clock_data {__u64 clock;__u32 flags; -__u32 pad[9 ]; +__u32 pad0; +__u64 realtime; +__u64 host_tsc; +__u32 pad[4 ]; };/* For KVM_CAP_SW_TLB */
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 2/13 KVM: x86: Refactor tsc synchronization code
In reply to Oliver UptonRefactor kvm_synchronize_tsc to make a new function that allows callers to specify TSC parameters (offset, value, nanoseconds, etc.) explicitly for the sake of participating in TSC synchronization.
This changes the locking semantics around TSC writes. Writes to the TSC will now take the pvclock gtod lock while holding the tsc write lock, whereas before these locks were disjoint.
--- Documentation/virt/kvm/locking.rst | 11 +++ arch/x86/kvm/x86.c | 106 +++++++++++++++++------------ 2 files changed, 74 insertions(+), 43 deletions(-)
Documentation/virt/kvm/locking.rst +11 -0
@@ -36,6 +36,9 @@ On x86: holding kvm->arch.mmu_lock (typically with ``read_lock``, otherwise there's no need to take kvm->arch.tdp_mmu_pages_lock at all). +- kvm->arch.tsc_write_lock is taken outside + kvm->arch.pvclock_gtod_sync_lock + Everything else is a leaf: no other lock is taken inside the critical sections.
@@ -222,6 +225,14 @@ time it will be set using the Dirty tracking mechanism described above. :Comment: 'raw' because hardware enabling/disabling must be atomic /wrt migration. +:Name: kvm_arch::pvclock_gtod_sync_lock +:Type: raw_spinlock_t +:Arch: x86 +:Protects: kvm_arch::{cur_tsc_generation,cur_tsc_nsec,cur_tsc_write, + cur_tsc_offset,nr_vcpus_matched_tsc} +:Comment: 'raw' because updating the kvm master clock must not be + preempted. + :Name: kvm_arch::tsc_write_lock :Type: raw_spinlock :Arch: x86
arch/x86/kvm/x86.c +63 -43
127 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 3/13 KVM: x86: Expose TSC offset controls to userspace
In reply to Oliver UptonTo date, VMM-directed TSC synchronization and migration has been a bit messy. KVM has some baked-in heuristics around TSC writes to infer if the VMM is attempting to synchronize. This is problematic, as it depends on host userspace writing to the guest's TSC within 1 second of the last write.
A much cleaner approach to configuring the guest's views of the TSC is to simply migrate the TSC offset for every vCPU. Offsets are idempotent, and thus not subject to change depending on when the VMM actually reads/writes values from/to KVM. The VMM can then read the TSC once with KVM_GET_CLOCK to capture a (realtime, host_tsc) pair at the instant when the guest is paused.
--- Documentation/virt/kvm/devices/vcpu.rst | 57 ++++++++ arch/x86/include/asm/kvm_host.h | 1 + arch/x86/include/uapi/asm/kvm.h | 4 + arch/x86/kvm/x86.c | 167 ++++++++++++++++++++++++ 4 files changed, 229 insertions(+)
Documentation/virt/kvm/devices/vcpu.rst +57 -0
@@ -161,3 +161,60 @@ Specifies the base address of the stolen time structure for this VCPU. The base address must be 64 byte aligned and exist within a valid guest memory region. See Documentation/virt/kvm/arm/pvtime.rst for more information including the layout of the stolen time structure. + +4. GROUP: KVM_VCPU_TSC_CTRL +=========================== + +:Architectures: x86 + +4.1 ATTRIBUTE: KVM_VCPU_TSC_OFFSET + +:Parameters: 64-bit unsigned TSC offset + +Returns: + + ======= ====================================== + -EFAULT Error reading/writing the provided + parameter address. + -ENXIO Attribute not supported + ======= ====================================== + +Specifies the guest's TSC offset relative to the host's TSC. The guest's +TSC is then derived by the following equation: + + guest_tsc = host_tsc + KVM_VCPU_TSC_OFFSET + +This attribute is useful for the precise migration of a guest's TSC. The +following describes a possible algorithm to use for the migration of a +guest's TSC: + +From the source VMM process: + +1. Invoke the KVM_GET_CLOCK ioctl to record the host TSC (t_0), + kvmclock nanoseconds (k_0), and realtime nanoseconds (r_0). + +2. Read the KVM_VCPU_TSC_OFFSET attribute for every vCPU to record the + guest TSC offset (off_n). + +3. Invoke the KVM_GET_TSC_KHZ ioctl to record the frequency of the + guest's TSC (freq). + +From the destination VMM process: + +4. Invoke the KVM_SET_CLOCK ioctl, providing the kvmclock nanoseconds + (k_0) and realtime nanoseconds (r_0) in their respective fields. + Ensure that the KVM_CLOCK_REALTIME flag is set in the provided + structure. KVM will advance the VM's kvmclock to account for elapsed + time since recording the clock values. + +5. Invoke the KVM_GET_CLOCK ioctl to record the host TSC (t_1) and + kvmclock nanoseconds (k_1). + +6. Adjust the guest TSC offsets for every vCPU to account for (1) time + elapsed since recording state and (2) difference in TSCs between the + source and destination machine: + + new_off_n = t_0 + off_n = (k_1 - k_0) * freq - t_1 + +7. Write the KVM_VCPU_TSC_OFFSET attribute for every vCPU with the + respective value derived in the previous step.
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1070,6 +1070,7 @@ struct kvm_arch {u64 last_tsc_nsec;u64 last_tsc_write;u32 last_tsc_khz; +u64 last_tsc_offset;u64 cur_tsc_nsec;u64 cur_tsc_write;u64 cur_tsc_offset;
arch/x86/include/uapi/asm/kvm.h +4 -0
@@ -503,4 +503,8 @@ struct kvm_pmu_event_filter {#define KVM_PMU_EVENT_ALLOW 0#define KVM_PMU_EVENT_DENY 1 +/* for KVM_{GET,SET,HAS}_DEVICE_ATTR */ +#define KVM_VCPU_TSC_CTRL 0/* control group for the timestamp counter (TSC) */ +#define KVM_VCPU_TSC_OFFSET 0/* attribute for the TSC offset */ +#endif /* _ASM_X86_KVM_H */
arch/x86/kvm/x86.c +167 -0
191 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
Paolo Bonzini
maintainerRe: [PATCH v4 03/13] KVM: x86: Expose TSC offset controls to userspace
Documentation/virt/kvm/devices/vcpu.rst Specifies the base address of the stolen time structure for this VCPU. The · line 217
Quoted 5 lines · Oliver Upton
+6. Adjust the guest TSC offsets for every vCPU to account for (1) time
Documentation/virt/kvm/devices/vcpu.rst +4
-0+ elapsed since recording state and (2) difference in TSCs between the + source and destination machine: + + new_off_n = t_0 + off_n = (k_1 - k_0) * freq - t_1
The second = should be a +.
Otherwise the algorithm seems correct.
Quoted 1 line
+
PATCH v4 4/13 tools: arch: x86: pull in pvclock headers
In reply to Oliver UptonCopy over approximately clean versions of the pvclock headers into tools. Reconcile headers/symbols missing in tools that are unneeded.
--- tools/arch/x86/include/asm/pvclock-abi.h | 48 +++++++++++ tools/arch/x86/include/asm/pvclock.h | 103 +++++++++++++++++++++++ 2 files changed, 151 insertions(+) create mode 100644 tools/arch/x86/include/asm/pvclock-abi.h create mode 100644 tools/arch/x86/include/asm/pvclock.h
tools/arch/x86/include/asm/pvclock-abi.h new file +48 -0
@@ -0,0 +1,48 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef _ASM_X86_PVCLOCK_ABI_H +#define _ASM_X86_PVCLOCK_ABI_H +#ifndef __ASSEMBLY__ + +/* +* These structs MUST NOT be changed. +* They are the ABI between hypervisor and guest OS. +* Both Xen and KVM are using this. +* +* pvclock_vcpu_time_info holds the system time and the tsc timestamp +* of the last update. So the guest can use the tsc delta to get a +* more precise system time. There is one per virtual cpu. +* +* pvclock_wall_clock references the point in time when the system +* time was zero (usually boot time), thus the guest calculates the +* current wall clock by adding the system time. +* +* Protocol for the "version" fields is: hypervisor raises it (making +* it uneven) before it starts updating the fields and raises it again +* (making it even) when it is done. Thus the guest can make sure the +* time values it got are consistent by checking the version before +* and after reading them. +*/ + +struct pvclock_vcpu_time_info { +u32 version; +u32 pad0; +u64 tsc_timestamp; +u64 system_time; +u32 tsc_to_system_mul; +s8 tsc_shift; +u8 flags; +u8 pad[2 ]; +} __attribute__((__packed__ ));/* 32 bytes */ + +struct pvclock_wall_clock { +u32 version; +u32 sec; +u32 nsec; +} __attribute__((__packed__ )); + +#define PVCLOCK_TSC_STABLE_BIT (1 << 0) +#define PVCLOCK_GUEST_STOPPED (1 << 1) +/* PVCLOCK_COUNTS_FROM_ZERO broke ABI and can't be used anymore. */ +#define PVCLOCK_COUNTS_FROM_ZERO (1 << 2) +#endif /* __ASSEMBLY__ */ +#endif /* _ASM_X86_PVCLOCK_ABI_H */
tools/arch/x86/include/asm/pvclock.h new file +103 -0
103 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 5/13 selftests: KVM: Add test for KVM_{GET,SET}_CLOCK
In reply to Oliver UptonAdd a selftest for the new KVM clock UAPI that was introduced. Ensure that the KVM clock is consistent between userspace and the guest, and that the difference in realtime will only ever cause the KVM clock to advance forward.
--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../testing/selftests/kvm/include/kvm_util.h | 2 + .../selftests/kvm/x86_64/kvm_clock_test.c | 204 ++++++++++++++++++ 4 files changed, 208 insertions(+) create mode 100644 tools/testing/selftests/kvm/x86_64/kvm_clock_test.c
tools/testing/selftests/kvm/.gitignore +1 -0
@@ -11,6 +11,7 @@ /x86_64/emulator_error_test /x86_64/get_cpuid_test /x86_64/get_msr_index_features +/x86_64/kvm_clock_test /x86_64/kvm_pv_test /x86_64/hyperv_clock /x86_64/hyperv_cpuid
tools/testing/selftests/kvm/Makefile +1 -0
@@ -46,6 +46,7 @@ TEST_GEN_PROGS_x86_64 += x86_64/get_cpuid_test TEST_GEN_PROGS_x86_64 += x86_64/hyperv_clock TEST_GEN_PROGS_x86_64 += x86_64/hyperv_cpuid TEST_GEN_PROGS_x86_64 += x86_64/hyperv_features +TEST_GEN_PROGS_x86_64 += x86_64/kvm_clock_test TEST_GEN_PROGS_x86_64 += x86_64/kvm_pv_test TEST_GEN_PROGS_x86_64 += x86_64/mmio_warning_test TEST_GEN_PROGS_x86_64 += x86_64/mmu_role_test
tools/testing/selftests/kvm/include/kvm_util.h +2 -0
@@ -19,6 +19,8 @@#define KVM_DEV_PATH "/dev/kvm"#define KVM_MAX_VCPUS 512 +#define NSEC_PER_SEC 1000000000L +/* * Callers of kvm_util only have an incomplete/opaque description of the * structure kvm_util is using to maintain the state of a VM.
tools/testing/selftests/kvm/x86_64/kvm_clock_test.c new file +204 -0
204 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 6/13 selftests: KVM: Fix kvm device helper ioctl assertions
In reply to Oliver UptonThe KVM_CREATE_DEVICE and KVM_{GET,SET}_DEVICE_ATTR ioctls are defined to return a value of zero on success. As such, tighten the assertions in the helper functions to only pass if the return code is zero.
--- tools/testing/selftests/kvm/lib/kvm_util.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/lib/kvm_util.c +3 -3
@@ -1984,7 +1984,7 @@ int kvm_device_check_attr(int dev_fd, uint32_t group, uint64_t attr) {int ret =_kvm_device_check_attr (dev_fd, group, attr); -TEST_ASSERT (ret >=0 ,"KVM_HAS_DEVICE_ATTR failed, rc: %i errno: %i" , ret, errno); +TEST_ASSERT (!ret,"KVM_HAS_DEVICE_ATTR failed, rc: %i errno: %i" , ret, errno);return ret; }
@@ -2008,7 +2008,7 @@ int kvm_create_device(struct kvm_vm *vm, uint64_t type, bool test) ret =_kvm_create_device (vm, type, test, &fd);if (!test) { -TEST_ASSERT (ret >=0 , +TEST_ASSERT (!ret,"KVM_CREATE_DEVICE IOCTL failed, rc: %i errno: %i" , ret, errno);return fd; }
@@ -2036,7 +2036,7 @@ int kvm_device_access(int dev_fd, uint32_t group, uint64_t attr, {int ret =_kvm_device_access (dev_fd, group, attr, val, write); -TEST_ASSERT (ret >=0 ,"KVM_SET|GET_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno); +TEST_ASSERT (!ret,"KVM_SET|GET_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno);return ret; }
Signature · 1 line
2.32.0.432.gabb21c7263-goog
Re: [PATCH v4 06/13] selftests: KVM: Fix kvm device helper ioctl assertions
Quoted 44 lines · Oliver Upton
The
KVM_CREATE_DEVICEand KVM_{GET,SET}_DEVICE_ATTR ioctls are defined to return a value of zero on success. As such, tighten the assertions in the helper functions to only pass if the return code is zero.Suggested-by Andrew Jones <[email protected]>Signed-off-by Oliver Upton <[email protected]>--- tools/testing/selftests/kvm/lib/kvm_util.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)tools/testing/selftests/kvm/lib/kvm_util.c +3
-3@@ -1984,7 +1984,7 @@ int kvm_device_check_attr(int dev_fd, uint32_t group, uint64_t attr) {int ret =_kvm_device_check_attr (dev_fd, group, attr); -TEST_ASSERT (ret >=0 ,"KVM_HAS_DEVICE_ATTR failed, rc: %i errno: %i" , ret, errno); +TEST_ASSERT (!ret,"KVM_HAS_DEVICE_ATTR failed, rc: %i errno: %i" , ret, errno);return ret; }@@ -2008,7 +2008,7 @@ int kvm_create_device(struct kvm_vm *vm, uint64_t type, bool test) ret =_kvm_create_device (vm, type, test, &fd);if (!test) { -TEST_ASSERT (ret >=0 , +TEST_ASSERT (!ret,"KVM_CREATE_DEVICE IOCTL failed, rc: %i errno: %i" , ret, errno);return fd; }@@ -2036,7 +2036,7 @@ int kvm_device_access(int dev_fd, uint32_t group, uint64_t attr, {int ret =_kvm_device_access (dev_fd, group, attr, val, write); -TEST_ASSERT (ret >=0 ,"KVM_SET|GET_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno); +TEST_ASSERT (!ret,"KVM_SET|GET_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno);return ret; }Signature · 1 line
2.32.0.432.gabb21c7263-goog
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v4 7/13 selftests: KVM: Add helpers for vCPU device attributes
In reply to Oliver UptonvCPU file descriptors are abstracted away from test code in KVM selftests, meaning that tests cannot directly access a vCPU's device attributes. Add helpers that tests can use to get at vCPU device attributes.
--- .../testing/selftests/kvm/include/kvm_util.h | 9 +++++ tools/testing/selftests/kvm/lib/kvm_util.c | 38 +++++++++++++++++++ 2 files changed, 47 insertions(+)
tools/testing/selftests/kvm/include/kvm_util.h +9 -0
@@ -240,6 +240,15 @@ int _kvm_device_access(int dev_fd, uint32_t group, uint64_t attr,int kvm_device_access (int dev_fd,uint32_t group,uint64_t attr,void *val,bool write); +int _vcpu_has_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr); +int vcpu_has_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr); +int _vcpu_access_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr,void *val,bool write); +int vcpu_access_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr,void *val,bool write); +const char *exit_reason_str (unsigned int exit_reason);void virt_pgd_alloc (struct kvm_vm *vm);
tools/testing/selftests/kvm/lib/kvm_util.c +38 -0
@@ -2040,6 +2040,44 @@ int kvm_device_access(int dev_fd, uint32_t group, uint64_t attr,return ret; } +int _vcpu_has_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr) +{ +struct vcpu *vcpu =vcpu_find (vm, vcpuid); + +TEST_ASSERT (vcpu,"nonexistent vcpu id: %d" , vcpuid); + +return _kvm_device_check_attr (vcpu->fd, group, attr); +} + +int vcpu_has_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr) +{ +int ret =_vcpu_has_device_attr (vm, vcpuid, group, attr); + +TEST_ASSERT (!ret,"KVM_HAS_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno); +return ret; +} + +int _vcpu_access_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr,void *val,bool write) +{ +struct vcpu *vcpu =vcpu_find (vm, vcpuid); + +TEST_ASSERT (vcpu,"nonexistent vcpu id: %d" , vcpuid); + +return _kvm_device_access (vcpu->fd, group, attr, val, write); +} + +int vcpu_access_device_attr (struct kvm_vm *vm,uint32_t vcpuid,uint32_t group, +uint64_t attr,void *val,bool write) +{ +int ret =_vcpu_access_device_attr (vm, vcpuid, group, attr, val, write); + +TEST_ASSERT (!ret,"KVM_SET|GET_DEVICE_ATTR IOCTL failed, rc: %i errno: %i" , ret, errno); +return ret; +} +/* * VM Dump *
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 8/13 selftests: KVM: Introduce system counter offset test
In reply to Oliver UptonIntroduce a KVM selftest to verify that userspace manipulation of the TSC (via the new vCPU attribute) results in the correct behavior within the guest.
--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../kvm/system_counter_offset_test.c | 132 ++++++++++++++++++ 3 files changed, 134 insertions(+) create mode 100644 tools/testing/selftests/kvm/system_counter_offset_test.c
tools/testing/selftests/kvm/.gitignore +1 -0
@@ -52,3 +52,4 @@ /set_memory_region_test /steal_time /kvm_binary_stats_test +/system_counter_offset_test
tools/testing/selftests/kvm/Makefile +1 -0
@@ -85,6 +85,7 @@ TEST_GEN_PROGS_x86_64 += memslot_perf_test TEST_GEN_PROGS_x86_64 += set_memory_region_test TEST_GEN_PROGS_x86_64 += steal_time TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test +TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_aarch64 += aarch64/debug-exceptions TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list
tools/testing/selftests/kvm/system_counter_offset_test.c new file +132 -0
132 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 9/13 KVM: arm64: Allow userspace to configure a vCPU's virtual offset
In reply to Oliver UptonAdd a new vCPU attribute that allows userspace to directly manipulate the virtual counter-timer offset. Exposing such an interface allows for the precise migration of guest virtual counter-timers, as it is an indepotent interface.
Uphold the existing behavior of writes to CNTVOFF_EL2 for this new interface, wherein a write to a single vCPU is broadcasted to all vCPUs within a VM.
--- Documentation/virt/kvm/devices/vcpu.rst | 22 ++++++++ arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/arch_timer.c | 68 ++++++++++++++++++++++++- 3 files changed, 89 insertions(+), 2 deletions(-)
Documentation/virt/kvm/devices/vcpu.rst +22 -0
@@ -139,6 +139,28 @@ configured values on other VCPUs. Userspace should configure the interrupt numbers on at least one VCPU after creating all VCPUs and before running any VCPUs. +2.2. ATTRIBUTE: KVM_ARM_VCPU_TIMER_OFFSET_VTIMER +------------------------------------------------ + +:Parameters: Pointer to a 64-bit unsigned counter-timer offset. + +Returns: + + ======= ====================================== + -EFAULT Error reading/writing the provided + parameter address + -ENXIO Attribute not supported + ======= ====================================== + +Specifies the guest's virtual counter-timer offset from the host's +virtual counter. The guest's virtual counter is then derived by +the following equation: + + guest_cntvct = host_cntvct - KVM_ARM_VCPU_TIMER_OFFSET_VTIMER + +KVM does not allow the use of varying offset values for different vCPUs; +the last written offset value will be broadcasted to all vCPUs in a VM. + 3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL ==================================
arch/arm64/include/uapi/asm/kvm.h +1 -0
@@ -365,6 +365,7 @@ struct kvm_arm_copy_mte_tags {#define KVM_ARM_VCPU_TIMER_CTRL 1#define KVM_ARM_VCPU_TIMER_IRQ_VTIMER 0#define KVM_ARM_VCPU_TIMER_IRQ_PTIMER 1 +#define KVM_ARM_VCPU_TIMER_OFFSET_VTIMER 2#define KVM_ARM_VCPU_PVTIME_CTRL 2#define KVM_ARM_VCPU_PVTIME_IPA 0
arch/arm64/kvm/arch_timer.c +66 -2
91 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 10/13 selftests: KVM: Add support for aarch64 to system_counter_offset_test
In reply to Oliver UptonKVM/arm64 now allows userspace to adjust the guest virtual counter-timer via a vCPU device attribute. Test that changes to the virtual counter-timer offset result in the correct view being presented to the guest.
--- tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/aarch64/processor.h | 12 +++++ .../kvm/system_counter_offset_test.c | 54 ++++++++++++++++++- 3 files changed, 66 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/Makefile +1 -0
@@ -98,6 +98,7 @@ TEST_GEN_PROGS_aarch64 += kvm_page_table_test TEST_GEN_PROGS_aarch64 += set_memory_region_test TEST_GEN_PROGS_aarch64 += steal_time TEST_GEN_PROGS_aarch64 += kvm_binary_stats_test +TEST_GEN_PROGS_aarch64 += system_counter_offset_test TEST_GEN_PROGS_s390x = s390x/memop TEST_GEN_PROGS_s390x += s390x/resets
tools/testing/selftests/kvm/include/aarch64/processor.h +12 -0
@@ -129,4 +129,16 @@ void vm_install_sync_handler(struct kvm_vm *vm,#define isb () asm volatile("isb" : : : "memory") +static inline uint64_t read_cntvct_ordered (void ) +{ +uint64_t r; + + __asm__ __volatile__("isb\n\t" +"mrs %0, cntvct_el0\n\t" +"isb\n\t" + :"=r" (r)); + +return r; +} +#endif /* SELFTEST_KVM_PROCESSOR_H */
tools/testing/selftests/kvm/system_counter_offset_test.c +53 -1
60 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 11/13 KVM: arm64: Provide userspace access to the physical counter offset
In reply to Oliver UptonPresently, KVM provides no facilities for correctly migrating a guest that depends on the physical counter-timer. While most guests (barring NV, of course) should not depend on the physical counter-timer, an operator may still wish to provide a consistent view of the physical counter-timer across migrations.
Provide userspace with a new vCPU attribute to modify the guest physical counter-timer offset. Since the base architecture doesn't provide a physical counter-timer offset register, emulate the correct behavior by trapping accesses to the physical counter-timer whenever the offset value is non-zero.
Uphold the same behavior as CNTVOFF_EL2 and broadcast the physical offset to all vCPUs whenever written. This guarantees that the counter-timer we provide the guest remains architectural, wherein all views of the counter-timer are consistent across vCPUs. Reconfigure timer traps for VHE on every guest entry, as different VMs will now have different traps enabled. Enable physical counter traps for nVHE whenever the offset is nonzero (we already trap physical timer registers in nVHE).
FEAT_ECV provides a guest physical counter-timer offset register (CNTPOFF_EL2), but ECV-enabled hardware is nonexistent at the time of writing so support for it was elided for the sake of the author :)
--- Documentation/virt/kvm/devices/vcpu.rst | 22 +++++++ arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/include/asm/kvm_hyp.h | 2 - arch/arm64/include/asm/sysreg.h | 1 + arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/arch_timer.c | 72 ++++++++++++++--------- arch/arm64/kvm/arm.c | 4 +- arch/arm64/kvm/hyp/include/hyp/switch.h | 23 ++++++++ arch/arm64/kvm/hyp/include/hyp/timer-sr.h | 26 ++++++++ arch/arm64/kvm/hyp/nvhe/switch.c | 2 - arch/arm64/kvm/hyp/nvhe/timer-sr.c | 21 +++---- arch/arm64/kvm/hyp/vhe/timer-sr.c | 27 +++++++++ include/kvm/arm_arch_timer.h | 2 - 13 files changed, 158 insertions(+), 46 deletions(-) create mode 100644 arch/arm64/kvm/hyp/include/hyp/timer-sr.h
Documentation/virt/kvm/devices/vcpu.rst +22 -0
@@ -161,6 +161,28 @@ the following equation: KVM does not allow the use of varying offset values for different vCPUs; the last written offset value will be broadcasted to all vCPUs in a VM. +2.3. ATTRIBUTE: KVM_ARM_VCPU_TIMER_OFFSET_PTIMER +------------------------------------------------ + +:Parameters: Pointer to a 64-bit unsigned counter-timer offset. + +Returns: + + ======= ====================================== + -EFAULT Error reading/writing the provided + parameter address + -ENXIO Attribute not supported + ======= ====================================== + +Specifies the guest's physical counter-timer offset from the host's +virtual counter. The guest's physical counter is then derived by +the following equation: + + guest_cntpct = host_cntvct - KVM_ARM_VCPU_TIMER_OFFSET_PTIMER + +KVM does not allow the use of varying offset values for different vCPUs; +the last written offset value will be broadcasted to all vCPUs in a VM. + 3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL ==================================
arch/arm64/include/asm/kvm_host.h +1 -0
@@ -204,6 +204,7 @@ enum vcpu_sysreg {SP_EL1 ,SPSR_EL1 , +CNTPOFF_EL2 ,CNTVOFF_EL2 ,CNTV_CVAL_EL0 , CNTV_CTL_EL0,
arch/arm64/include/asm/kvm_hyp.h +0 -2
@@ -65,10 +65,8 @@ void __vgic_v3_save_aprs(struct vgic_v3_cpu_if *cpu_if);void __vgic_v3_restore_aprs (struct vgic_v3_cpu_if *cpu_if);int __vgic_v3_perform_cpuif_access (struct kvm_vcpu *vcpu); -#ifdef __KVM_NVHE_HYPERVISOR__void __timer_enable_traps (struct kvm_vcpu *vcpu);void __timer_disable_traps (struct kvm_vcpu *vcpu); -#endif #ifdef __KVM_NVHE_HYPERVISOR__void __sysreg_save_state_nvhe (struct kvm_cpu_context *ctxt);
arch/arm64/include/asm/sysreg.h +1 -0
@@ -505,6 +505,7 @@#define SYS_AMEVCNTR0_MEM_STALL SYS_AMEVCNTR0_EL0(3)#define SYS_CNTFRQ_EL0 sys_reg(3, 3, 14, 0, 0) +#define SYS_CNTPCT_EL0 sys_reg(3, 3, 14, 0, 1)#define SYS_CNTP_TVAL_EL0 sys_reg(3, 3, 14, 2, 0)#define SYS_CNTP_CTL_EL0 sys_reg(3, 3, 14, 2, 1)
arch/arm64/include/uapi/asm/kvm.h +1 -0
@@ -366,6 +366,7 @@ struct kvm_arm_copy_mte_tags {#define KVM_ARM_VCPU_TIMER_IRQ_VTIMER 0#define KVM_ARM_VCPU_TIMER_IRQ_PTIMER 1#define KVM_ARM_VCPU_TIMER_OFFSET_VTIMER 2 +#define KVM_ARM_VCPU_TIMER_OFFSET_PTIMER 3#define KVM_ARM_VCPU_PVTIME_CTRL 2#define KVM_ARM_VCPU_PVTIME_IPA 0
arch/arm64/kvm/arch_timer.c +45 -27
149 lines not on this page · raw message
arch/arm64/kvm/arm.c +1 -3
@@ -1558,9 +1558,7 @@ static void cpu_hyp_reinit(void)cpu_hyp_reset (); -if (is_kernel_in_hyp_mode ()) -kvm_timer_init_vhe (); -else +if (!is_kernel_in_hyp_mode ())cpu_init_hyp_mode ();cpu_set_hyp_vector ();
arch/arm64/kvm/hyp/include/hyp/switch.h +23 -0
@@ -8,6 +8,7 @@#define __ARM64_KVM_HYP_SWITCH_H__#include <hyp/adjust_pc.h> +#include <hyp/timer-sr.h> #include <linux/arm-smccc.h> #include <linux/kvm_host.h>
@@ -113,6 +114,8 @@ static inline void ___activate_traps(struct kvm_vcpu *vcpu)if (cpus_have_final_cap (ARM64_HAS_RAS_EXTN ) && (hcr &HCR_VSE ))write_sysreg_s (vcpu->arch.vsesr_el2,SYS_VSESR_EL2 ); + +__timer_enable_traps (vcpu); }static inline void ___deactivate_traps (struct kvm_vcpu *vcpu)
@@ -127,6 +130,8 @@ static inline void ___deactivate_traps(struct kvm_vcpu *vcpu) vcpu->arch.hcr_el2 &= ~HCR_VSE ; vcpu->arch.hcr_el2 |=read_sysreg (hcr_el2) &HCR_VSE ; } + +__timer_disable_traps (vcpu); }static inline bool __translate_far_to_hpfar (u64 far,u64 *hpfar)
@@ -405,6 +410,21 @@ static inline bool __hyp_handle_ptrauth(struct kvm_vcpu *vcpu)return true; } +static inline bool __hyp_handle_counter (struct kvm_vcpu *vcpu) +{ +u32 sysreg =esr_sys64_to_sysreg (kvm_vcpu_get_esr (vcpu)); +int rt =kvm_vcpu_sys_get_rt (vcpu); +u64 rv; + +if (sysreg !=SYS_CNTPCT_EL0 ) +return false; + + rv =__timer_read_cntpct (vcpu); +vcpu_set_reg (vcpu, rt, rv); +__kvm_skip_instr (vcpu); +return true; +} +/* * Return true when we were able to fixup the guest exit and should return to * the guest, false when we should restore the host state and return to the
@@ -439,6 +459,9 @@ static inline bool fixup_guest_exit(struct kvm_vcpu *vcpu, u64 *exit_code)if (*exit_code !=ARM_EXCEPTION_TRAP ) goto exit; +if (__hyp_handle_counter (vcpu)) + goto guest; +if (cpus_have_final_cap (ARM64_WORKAROUND_CAVIUM_TX2_219_TVM ) &&kvm_vcpu_trap_get_class (vcpu) == ESR_ELx_EC_SYS64 &&handle_tx2_tvm (vcpu))
arch/arm64/kvm/hyp/include/hyp/timer-sr.h new file +26 -0
@@ -0,0 +1,26 @@ +/* SPDX-License-Identifier: GPL-2.0-only */ +/* +* Copyright (C) 2021 Google LLC +* Author: Oliver Upton <[email protected]> +*/ + +#ifndef __ARM64_KVM_HYP_TIMER_SR_H__ +#define __ARM64_KVM_HYP_TIMER_SR_H__ + +#include <linux/compiler.h> +#include <linux/kvm_host.h> + +#include <asm/kvm_asm.h> +#include <asm/kvm_hyp.h> + +static inline bool __timer_physical_emulation_required (struct kvm_vcpu *vcpu) +{ +return __vcpu_sys_reg (vcpu,CNTPOFF_EL2 ); +} + +static inline u64 __timer_read_cntpct (struct kvm_vcpu *vcpu) +{ +return read_sysreg (cntpct_el0) -__vcpu_sys_reg (vcpu,CNTPOFF_EL2 ); +} + +#endif /* __ARM64_KVM_HYP_TIMER_SR_H__ */
arch/arm64/kvm/hyp/nvhe/switch.c +0 -2
@@ -217,7 +217,6 @@ int __kvm_vcpu_run(struct kvm_vcpu *vcpu)__activate_traps (vcpu);__hyp_vgic_restore_state (vcpu); -__timer_enable_traps (vcpu);__debug_switch_to_guest (vcpu);
@@ -230,7 +229,6 @@ int __kvm_vcpu_run(struct kvm_vcpu *vcpu)__sysreg_save_state_nvhe (guest_ctxt);__sysreg32_save_state (vcpu); -__timer_disable_traps (vcpu);__hyp_vgic_save_state (vcpu);__deactivate_traps (vcpu);
arch/arm64/kvm/hyp/nvhe/timer-sr.c +11 -10
@@ -9,16 +9,13 @@#include <linux/kvm_host.h> #include <asm/kvm_hyp.h> +#include <hyp/timer-sr.h> void __kvm_timer_set_cntvoff (u64 cntvoff) {write_sysreg (cntvoff, cntvoff_el2); } -/* -* Should only be called on non-VHE systems. -* VHE systems use EL2 timers and configure EL1 timers in kvm_timer_init_vhe(). -*/ void __timer_disable_traps (struct kvm_vcpu *vcpu) {u64 val;
@@ -29,20 +26,24 @@ void __timer_disable_traps(struct kvm_vcpu *vcpu)write_sysreg (val, cnthctl_el2); } -/* -* Should only be called on non-VHE systems. -* VHE systems use EL2 timers and configure EL1 timers in kvm_timer_init_vhe(). -*/ void __timer_enable_traps (struct kvm_vcpu *vcpu) {u64 val;/* * Disallow physical timer access for the guest -* Physical counter access is allowed */ val =read_sysreg (cnthctl_el2); val &= ~CNTHCTL_EL1PCEN ; - val |=CNTHCTL_EL1PCTEN ; + +/* +* Disallow physical counter access for the guest if offsetting is +* requested. +*/ +if (__timer_physical_emulation_required (vcpu)) + val &= ~CNTHCTL_EL1PCTEN ; +else + val |=CNTHCTL_EL1PCTEN ; +write_sysreg (val, cnthctl_el2); }
arch/arm64/kvm/hyp/vhe/timer-sr.c +27 -0
@@ -4,9 +4,36 @@* Author: Marc Zyngier <[email protected]> */ +#include <asm/kvm_host.h> #include <asm/kvm_hyp.h> +#include <hyp/timer-sr.h> void __kvm_timer_set_cntvoff (u64 cntvoff) {write_sysreg (cntvoff, cntvoff_el2); } + +void __timer_enable_traps (struct kvm_vcpu *vcpu) +{ +/* When HCR_EL2.E2H == 1, EL1PCEN nad EL1PCTEN are shifted by 10 */ +u32 cnthctl_shift =10 ; +u64 val, mask; + + mask =CNTHCTL_EL1PCEN << cnthctl_shift; + mask |=CNTHCTL_EL1PCTEN << cnthctl_shift; + + val =read_sysreg (cnthctl_el2); + +/* +* VHE systems allow the guest direct access to the EL1 physical +* timer/counter if offsetting isn't requested. +*/ +if (__timer_physical_emulation_required (vcpu)) + val &= ~mask; +else + val |= mask; + +write_sysreg (val, cnthctl_el2); +} + +void __timer_disable_traps (struct kvm_vcpu *vcpu) {}
include/kvm/arm_arch_timer.h +0 -2
@@ -83,8 +83,6 @@ u64 kvm_phys_timer_read(void);void kvm_timer_vcpu_load (struct kvm_vcpu *vcpu);void kvm_timer_vcpu_put (struct kvm_vcpu *vcpu); -void kvm_timer_init_vhe (void ); -bool kvm_arch_timer_get_input_level (int vintid);#define vcpu_timer (v) (&(v)->arch.timer_cpu)
Signature · 1 line
2.32.0.432.gabb21c7263-goog
Re: [PATCH v4 11/13] KVM: arm64: Provide userspace access to the physical counter offset
Quoted 27 lines · Oliver Upton
Presently, KVM provides no facilities for correctly migrating a guest that depends on the physical counter-timer. While most guests (barring NV, of course) should not depend on the physical counter-timer, an operator may still wish to provide a consistent view of the physical counter-timer across migrations.
Provide userspace with a new vCPU attribute to modify the guest physical counter-timer offset. Since the base architecture doesn't provide a physical counter-timer offset register, emulate the correct behavior by trapping accesses to the physical counter-timer whenever the offset value is non-zero.
Uphold the same behavior as
CNTVOFF_EL2and broadcast the physical offset to all vCPUs whenever written. This guarantees that the counter-timer we provide the guest remains architectural, wherein all views of the counter-timer are consistent across vCPUs. Reconfigure timer traps for VHE on every guest entry, as different VMs will now have different traps enabled. Enable physical counter traps for nVHE whenever the offset is nonzero (we already trap physical timer registers in nVHE).
FEAT_ECVprovides a guest physical counter-timer offset register (CNTPOFF_EL2), but ECV-enabled hardware is nonexistent at the time of writing so support for it was elided for the sake of the author :)Cc Andrew Jones <[email protected]>Signed-off-by Oliver Upton <[email protected]>
Quoted 17 lines
--- Documentation/virt/kvm/devices/vcpu.rst | 22 +++++++ arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/include/asm/kvm_hyp.h | 2 - arch/arm64/include/asm/sysreg.h | 1 + arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/arch_timer.c | 72 ++++++++++++++--------- arch/arm64/kvm/arm.c | 4 +- arch/arm64/kvm/hyp/include/hyp/switch.h | 23 ++++++++ arch/arm64/kvm/hyp/include/hyp/timer-sr.h | 26 ++++++++ arch/arm64/kvm/hyp/nvhe/switch.c | 2 - arch/arm64/kvm/hyp/nvhe/timer-sr.c | 21 +++---- arch/arm64/kvm/hyp/vhe/timer-sr.c | 27 +++++++++ include/kvm/arm_arch_timer.h | 2 - 13 files changed, 158 insertions(+), 46 deletions(-) create mode 100644 arch/arm64/kvm/hyp/include/hyp/timer-sr.h
PATCH v4 12/13 selftests: KVM: Test physical counter offsetting
In reply to Oliver UptonTest that userpace adjustment of the guest physical counter-timer results in the correct view of within the guest.
--- .../selftests/kvm/include/aarch64/processor.h | 12 ++++++++ .../kvm/system_counter_offset_test.c | 29 ++++++++++++++++--- 2 files changed, 37 insertions(+), 4 deletions(-)
tools/testing/selftests/kvm/include/aarch64/processor.h +12 -0
@@ -141,4 +141,16 @@ static inline uint64_t read_cntvct_ordered(void) return r; } +static inline uint64_t read_cntpct_ordered (void ) +{ +uint64_t r; + + __asm__ __volatile__("isb\n\t" +"mrs %0, cntpct_el0\n\t" +"isb\n\t" + :"=r" (r)); + +return r; +} +#endif /* SELFTEST_KVM_PROCESSOR_H */
tools/testing/selftests/kvm/system_counter_offset_test.c +25 -4
@@ -57,6 +57,7 @@ static uint64_t host_read_guest_system_counter(struct test_case *test)enum arch_counter {VIRTUAL , +PHYSICAL , };struct test_case {
@@ -68,23 +69,41 @@ static struct test_case test_cases[] = { { .counter = VIRTUAL, .offset = 0 }, { .counter = VIRTUAL, .offset = 180 * NSEC_PER_SEC }, { .counter = VIRTUAL, .offset = -180 * NSEC_PER_SEC }, + { .counter = PHYSICAL, .offset = 0 }, + { .counter = PHYSICAL, .offset = 180 * NSEC_PER_SEC }, + { .counter = PHYSICAL, .offset = -180 * NSEC_PER_SEC }, };static void check_preconditions (struct kvm_vm *vm) {if (!_vcpu_has_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , -KVM_ARM_VCPU_TIMER_OFFSET_VTIMER )) +KVM_ARM_VCPU_TIMER_OFFSET_VTIMER ) && + !_vcpu_has_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , +KVM_ARM_VCPU_TIMER_OFFSET_PTIMER ))return ; -print_skip ("KVM_ARM_VCPU_TIMER_OFFSET_VTIMER not supported; skipping test" ); +print_skip ("KVM_ARM_VCPU_TIMER_OFFSET_{VTIMER,PTIMER} not supported; skipping test" );exit (KSFT_SKIP ); }static void setup_system_counter (struct kvm_vm *vm,struct test_case *test) { +u64 attr =0 ; + +switch (test->counter) { +case VIRTUAL : + attr =KVM_ARM_VCPU_TIMER_OFFSET_VTIMER ; +break ; +case PHYSICAL : + attr =KVM_ARM_VCPU_TIMER_OFFSET_PTIMER ; +break ; +default : +TEST_ASSERT (false,"unrecognized counter index %u" , + test->counter); + } +vcpu_access_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , -KVM_ARM_VCPU_TIMER_OFFSET_VTIMER , &test->offset, - true); + attr, &test->offset, true); }static uint64_t guest_read_system_counter (struct test_case *test)
@@ -92,6 +111,8 @@ static uint64_t guest_read_system_counter(struct test_case *test)switch (test->counter) {case VIRTUAL :return read_cntvct_ordered (); +case PHYSICAL : +return read_cntpct_ordered ();default :GUEST_ASSERT (0 ); }
Signature · 1 line
2.32.0.432.gabb21c7263-goog
PATCH v4 13/13 selftests: KVM: Add counter emulation benchmark
In reply to Oliver UptonAdd a test case for counter emulation on arm64. A side effect of how KVM handles physical counter offsetting on non-ECV systems is that the virtual counter will always hit hardware and the physical could be emulated. Force emulation by writing a nonzero offset to the physical counter and compare the elapsed cycles to a direct read of the hardware register.
--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../kvm/aarch64/counter_emulation_benchmark.c | 215 ++++++++++++++++++ 3 files changed, 217 insertions(+) create mode 100644 tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c
tools/testing/selftests/kvm/.gitignore +1 -0
@@ -1,5 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only /aarch64/debug-exceptions +/aarch64/counter_emulation_benchmark /aarch64/get-reg-list /aarch64/vgic_init /s390x/memop
tools/testing/selftests/kvm/Makefile +1 -0
@@ -88,6 +88,7 @@ TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_aarch64 += aarch64/debug-exceptions +TEST_GEN_PROGS_aarch64 += aarch64/counter_emulation_benchmark TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list TEST_GEN_PROGS_aarch64 += aarch64/vgic_init TEST_GEN_PROGS_aarch64 += demand_paging_test
tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c new file +215 -0
215 lines not on this page · raw message
Signature · 1 line
2.32.0.432.gabb21c7263-goog
Re: [PATCH v4 13/13] selftests: KVM: Add counter emulation benchmark
Quoted 263 lines · Oliver Upton
Add a test case for counter emulation on arm64. A side effect of how KVM handles physical counter offsetting on non-ECV systems is that the virtual counter will always hit hardware and the physical could be emulated. Force emulation by writing a nonzero offset to the physical counter and compare the elapsed cycles to a direct read of the hardware register.
Reviewed-by Ricardo Koller <[email protected]>Signed-off-by Oliver Upton <[email protected]>--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../kvm/aarch64/counter_emulation_benchmark.c | 215 ++++++++++++++++++ 3 files changed, 217 insertions(+) create mode 100644 tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.ctools/testing/selftests/kvm/.gitignore +1
-0@@ -1,5 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only /aarch64/debug-exceptions +/aarch64/counter_emulation_benchmark /aarch64/get-reg-list /aarch64/vgic_init /s390x/memoptools/testing/selftests/kvm/Makefile +1
-0@@ -88,6 +88,7 @@ TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_aarch64 += aarch64/debug-exceptions +TEST_GEN_PROGS_aarch64 += aarch64/counter_emulation_benchmark TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list TEST_GEN_PROGS_aarch64 += aarch64/vgic_init TEST_GEN_PROGS_aarch64 += demand_paging_testtools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c new file +215
-0@@ -0,0 +1,215 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* counter_emulation_benchmark.c -- test to measure the effects of counter +* emulation on guest reads of the physical counter. +* +* Copyright (c) 2021, Google LLC. +*/ + +#define _GNU_SOURCE +#include <asm/kvm.h> +#include <linux/kvm.h> +#include <stdio.h> +#include <stdint.h> +#include <stdlib.h> +#include <unistd.h> + +#include "kvm_util.h" +#include "processor.h" +#include "test_util.h" + +#define VCPU_ID 0 + +static struct counter_values { +uint64_t cntvct_start; +uint64_t cntpct; +uint64_t cntvct_end; +} counter_values; + +static uint64_t nr_iterations =1000 ; + +static void do_test (void ) +{ +/* +* Open-coded approach instead of using helper methods to keep a tight +* interval around the physical counter read. +*/ + asmvolatile ("isb\n\t" +"mrs %[cntvct_start], cntvct_el0\n\t" +"isb\n\t" +"mrs %[cntpct], cntpct_el0\n\t" +"isb\n\t" +"mrs %[cntvct_end], cntvct_el0\n\t" +"isb\n\t" + : [cntvct_start]"=r" (counter_values.cntvct_start), + [cntpct]"=r" (counter_values.cntpct), + [cntvct_end]"=r" (counter_values.cntvct_end)); +} + +static void guest_main (void ) +{ +int i; + +for (i =0 ; i < nr_iterations; i++) { +do_test (); +GUEST_SYNC (i); + } + +for (i =0 ; i < nr_iterations; i++) { +do_test (); +GUEST_SYNC (i); + } + +GUEST_DONE (); +} + +static bool enter_guest (struct kvm_vm *vm) +{ +struct ucall uc; + +vcpu_ioctl (vm,VCPU_ID ,KVM_RUN ,NULL ); + +switch (get_ucall (vm,VCPU_ID , &uc)) { +case UCALL_DONE : +return true; +case UCALL_SYNC : +break ; +case UCALL_ABORT : +TEST_ASSERT (false,"%s at %s:%ld" , (const char *)uc.args[0 ], + __FILE__, uc.args[1 ]); +break ; +default : +TEST_ASSERT (false,"unexpected exit: %s" , +exit_reason_str (vcpu_state (vm,VCPU_ID )->exit_reason)); +break ; + } + +/* more work to do in the guest */ +return false; +} + +static double counter_frequency (void ) +{ +uint32_t freq; + + asmvolatile ("mrs %0, cntfrq_el0" + :"=r" (freq)); + +return freq /1000000.0 ; +} + +static void log_csv (FILE *csv,bool trapped) +{ +double freq =counter_frequency (); + +fprintf (csv,"%s,%.02f,%lu,%lu,%lu\n" , + trapped ?"true" :"false" , freq, + counter_values.cntvct_start, + counter_values.cntpct, + counter_values.cntvct_end); +} + +static double run_loop (struct kvm_vm *vm,FILE *csv,bool trapped) +{ +double avg =0 ; +int i; + +for (i =0 ; i < nr_iterations; i++) { +uint64_t delta; + +TEST_ASSERT (!enter_guest (vm),"guest exited unexpectedly" ); +sync_global_from_guest (vm, counter_values); + +if (csv) +log_csv (csv, trapped); + + delta = counter_values.cntvct_end - counter_values.cntvct_start; + avg = ((avg * i) + delta) / (i +1 ); + } + +return avg; +} + +static void setup_counter (struct kvm_vm *vm,uint64_t offset) +{ +vcpu_access_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , +KVM_ARM_VCPU_TIMER_OFFSET_PTIMER , &offset, + true); +} + +static void run_tests (struct kvm_vm *vm,FILE *csv) +{ +double avg_trapped, avg_native, freq; + + freq =counter_frequency (); + +if (csv) +fputs ("trapped,freq_mhz,cntvct_start,cntpct,cntvct_end\n" , csv); + +/* no physical offsetting; kvm allows reads of cntpct_el0 */ +setup_counter (vm,0 ); + avg_native =run_loop (vm, csv, false); + +/* force emulation of the physical counter */ +setup_counter (vm,1 ); + avg_trapped =run_loop (vm, csv, true); + +TEST_ASSERT (enter_guest (vm),"guest didn't run to completion" ); +pr_info ("%lu iterations: average cycles (@%.02fMHz) native: %.02f, trapped: %.02f\n" , + nr_iterations, freq, avg_native, avg_trapped); +} + +static void usage (const char *program_name) +{ +fprintf (stderr, +"Usage: %s [-h] [-o csv_file] [-n iterations]\n" +" -h prints this message\n" +" -n number of test iterations (default: %lu)\n" +" -o csv file to write data\n" , + program_name, nr_iterations); +} + +int main (int argc,char **argv) +{ +struct kvm_vm *vm; +FILE *csv =NULL ; +int opt; + +while ((opt =getopt (argc, argv,"hn:o:" )) !=-1 ) { +switch (opt) { +case 'o' : + csv =fopen (optarg,"w" ); +if (!csv) { +fprintf (stderr,"failed to open file '%s': %d\n" , + optarg, errno); +exit (1 ); + } +break ; +case 'n' : + nr_iterations =strtoul (optarg,NULL ,0 ); +break ; +default : +fprintf (stderr,"unrecognized option: '-%c'\n" , opt); +/* fallthrough */ +case 'h' : +usage (argv[0 ]); +exit (1 ); + } + } + + vm =vm_create_default (VCPU_ID ,0 , guest_main); +sync_global_to_guest (vm, nr_iterations); +ucall_init (vm,NULL ); + +if (_vcpu_has_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , +KVM_ARM_VCPU_TIMER_OFFSET_PTIMER )) { +print_skip ("KVM_ARM_VCPU_TIMER_OFFSET_PTIMER not supported." ); +exit (KSFT_SKIP ); + } + +run_tests (vm, csv); +kvm_vm_free (vm); + +if (csv) +fclose (csv); +}Signature · 1 line
2.32.0.432.gabb21c7263-goog
I skimmed through this, but didn't see any changes from v3 where I had a couple comments.
Thanks,
drew
Re: [PATCH v4 13/13] selftests: KVM: Add counter emulation benchmark
Quoted 260 lines · Andrew Jones
Quoted 258 lines · Oliver Upton
Add a test case for counter emulation on arm64. A side effect of how KVM handles physical counter offsetting on non-ECV systems is that the virtual counter will always hit hardware and the physical could be emulated. Force emulation by writing a nonzero offset to the physical counter and compare the elapsed cycles to a direct read of the hardware register.
Reviewed-by Ricardo Koller <[email protected]>Signed-off-by Oliver Upton <[email protected]>--- tools/testing/selftests/kvm/.gitignore | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../kvm/aarch64/counter_emulation_benchmark.c | 215 ++++++++++++++++++ 3 files changed, 217 insertions(+) create mode 100644 tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.ctools/testing/selftests/kvm/.gitignore +1
-0@@ -1,5 +1,6 @@ # SPDX-License-Identifier: GPL-2.0-only /aarch64/debug-exceptions +/aarch64/counter_emulation_benchmark /aarch64/get-reg-list /aarch64/vgic_init /s390x/memoptools/testing/selftests/kvm/Makefile +1
-0@@ -88,6 +88,7 @@ TEST_GEN_PROGS_x86_64 += kvm_binary_stats_test TEST_GEN_PROGS_x86_64 += system_counter_offset_test TEST_GEN_PROGS_aarch64 += aarch64/debug-exceptions +TEST_GEN_PROGS_aarch64 += aarch64/counter_emulation_benchmark TEST_GEN_PROGS_aarch64 += aarch64/get-reg-list TEST_GEN_PROGS_aarch64 += aarch64/vgic_init TEST_GEN_PROGS_aarch64 += demand_paging_testtools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c new file +213
-0@@ -0,0 +1,215 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* counter_emulation_benchmark.c -- test to measure the effects of counter +* emulation on guest reads of the physical counter. +* +* Copyright (c) 2021, Google LLC. +*/ + +#define _GNU_SOURCE +#include <asm/kvm.h> +#include <linux/kvm.h> +#include <stdio.h> +#include <stdint.h> +#include <stdlib.h> +#include <unistd.h> + +#include "kvm_util.h" +#include "processor.h" +#include "test_util.h" + +#define VCPU_ID 0 + +static struct counter_values { +uint64_t cntvct_start; +uint64_t cntpct; +uint64_t cntvct_end; +} counter_values; + +static uint64_t nr_iterations =1000 ; + +static void do_test (void ) +{ +/* +* Open-coded approach instead of using helper methods to keep a tight +* interval around the physical counter read. +*/ + asmvolatile ("isb\n\t" +"mrs %[cntvct_start], cntvct_el0\n\t" +"isb\n\t" +"mrs %[cntpct], cntpct_el0\n\t" +"isb\n\t" +"mrs %[cntvct_end], cntvct_el0\n\t" +"isb\n\t" + : [cntvct_start]"=r" (counter_values.cntvct_start), + [cntpct]"=r" (counter_values.cntpct), + [cntvct_end]"=r" (counter_values.cntvct_end)); +} + +static void guest_main (void ) +{ +int i; + +for (i =0 ; i < nr_iterations; i++) { +do_test (); +GUEST_SYNC (i); + } + +for (i =0 ; i < nr_iterations; i++) { +do_test (); +GUEST_SYNC (i); + } + +GUEST_DONE (); +} + +static bool enter_guest (struct kvm_vm *vm) +{ +struct ucall uc; + +vcpu_ioctl (vm,VCPU_ID ,KVM_RUN ,NULL ); + +switch (get_ucall (vm,VCPU_ID , &uc)) { +case UCALL_DONE : +return true; +case UCALL_SYNC : +break ; +case UCALL_ABORT : +TEST_ASSERT (false,"%s at %s:%ld" , (const char *)uc.args[0 ], + __FILE__, uc.args[1 ]); +break ; +default : +TEST_ASSERT (false,"unexpected exit: %s" , +exit_reason_str (vcpu_state (vm,VCPU_ID )->exit_reason)); +break ; + } + +/* more work to do in the guest */ +return false; +} + +static double counter_frequency (void ) +{ +uint32_t freq; + + asmvolatile ("mrs %0, cntfrq_el0" + :"=r" (freq)); + +return freq /1000000.0 ; +} + +static void log_csv (FILE *csv,bool trapped) +{ +double freq =counter_frequency (); + +fprintf (csv,"%s,%.02f,%lu,%lu,%lu\n" , + trapped ?"true" :"false" , freq, + counter_values.cntvct_start, + counter_values.cntpct, + counter_values.cntvct_end); +} + +static double run_loop (struct kvm_vm *vm,FILE *csv,bool trapped) +{ +double avg =0 ; +int i; + +for (i =0 ; i < nr_iterations; i++) { +uint64_t delta; + +TEST_ASSERT (!enter_guest (vm),"guest exited unexpectedly" ); +sync_global_from_guest (vm, counter_values); + +if (csv) +log_csv (csv, trapped); + + delta = counter_values.cntvct_end - counter_values.cntvct_start; + avg = ((avg * i) + delta) / (i +1 ); + } + +return avg; +} + +static void setup_counter (struct kvm_vm *vm,uint64_t offset) +{ +vcpu_access_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , +KVM_ARM_VCPU_TIMER_OFFSET_PTIMER , &offset, + true); +} + +static void run_tests (struct kvm_vm *vm,FILE *csv) +{ +double avg_trapped, avg_native, freq; + + freq =counter_frequency (); + +if (csv) +fputs ("trapped,freq_mhz,cntvct_start,cntpct,cntvct_end\n" , csv); + +/* no physical offsetting; kvm allows reads of cntpct_el0 */ +setup_counter (vm,0 ); + avg_native =run_loop (vm, csv, false); + +/* force emulation of the physical counter */ +setup_counter (vm,1 ); + avg_trapped =run_loop (vm, csv, true); + +TEST_ASSERT (enter_guest (vm),"guest didn't run to completion" ); +pr_info ("%lu iterations: average cycles (@%.02fMHz) native: %.02f, trapped: %.02f\n" , + nr_iterations, freq, avg_native, avg_trapped); +} + +static void usage (const char *program_name) +{ +fprintf (stderr, +"Usage: %s [-h] [-o csv_file] [-n iterations]\n" +" -h prints this message\n" +" -n number of test iterations (default: %lu)\n" +" -o csv file to write data\n" , + program_name, nr_iterations); +} + +int main (int argc,char **argv) +{ +struct kvm_vm *vm; +FILE *csv =NULL ; +int opt; + +while ((opt =getopt (argc, argv,"hn:o:" )) !=-1 ) { +switch (opt) { +case 'o' : + csv =fopen (optarg,"w" ); +if (!csv) { +fprintf (stderr,"failed to open file '%s': %d\n" , + optarg, errno); +exit (1 ); + } +break ; +case 'n' : + nr_iterations =strtoul (optarg,NULL ,0 ); +break ; +default : +fprintf (stderr,"unrecognized option: '-%c'\n" , opt); +/* fallthrough */ +case 'h' : +usage (argv[0 ]); +exit (1 ); + } + } + + vm =vm_create_default (VCPU_ID ,0 , guest_main); +sync_global_to_guest (vm, nr_iterations); +ucall_init (vm,NULL ); + +if (_vcpu_has_device_attr (vm,VCPU_ID ,KVM_ARM_VCPU_TIMER_CTRL , +KVM_ARM_VCPU_TIMER_OFFSET_PTIMER )) { +print_skip ("KVM_ARM_VCPU_TIMER_OFFSET_PTIMER not supported." ); +exit (KSFT_SKIP ); + } + +run_tests (vm, csv); +kvm_vm_free (vm); + +if (csv)
Quoted 8 lines
Quoted 5 lines
tools/testing/selftests/kvm/aarch64/counter_emulation_benchmark.c new file +2
-1+fclose (csv); +} --2.32.0.432.gabb21c7263-goog
I skimmed through this, but didn't see any changes from v3 where I had a couple comments.
Ah, yes, I missed those comments by accident. Thanks!
--
Oliver