diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/reasoning/KVM/1732959 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/reasoning/KVM/1732959')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/reasoning/KVM/1732959 | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/results/classifier/deepseek-2-tmp/reasoning/KVM/1732959 b/results/classifier/deepseek-2-tmp/reasoning/KVM/1732959 deleted file mode 100644 index 0c7e6ac5..00000000 --- a/results/classifier/deepseek-2-tmp/reasoning/KVM/1732959 +++ /dev/null @@ -1,14 +0,0 @@ -<think> -Okay, I need to classify this bug report from QEMU. Let me read through the details carefully. - -The user describes a problem where after resuming a VM (step #4), the source VM's clock jumps by several seconds, proportional to the time since the last migration. They mention that bisecting the issue points to commit 108b249c453dd7132599ab6dc7e435a7036c193f, which introduces a function get_kvmclock_ns in KVM's x86 code. - -So, this seems related to the way KVM handles timekeeping. The commit removes get_kernel_ns and replaces it with ktime_get_boot_ns, affecting how kvmclock is implemented as a thin veneer over TSC. This could be causing the clock jump when resuming the VM after migration. - -Looking at the categories provided: device, graphic, socket, network, KVM, etc. Since this issue is tied to KVM's time functions and affects how the guest OS perceives time during resume, it falls under the 'KVM' category. -</think> - -The bug report discusses an issue with KVM's handling of kvmclock after resuming a VM, which directly relates to the hypervisor's timekeeping mechanism. - -**Answer:** -KVM
\ No newline at end of file |