summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2/reasoning/peripherals/165
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2/reasoning/peripherals/165
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloademulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2/reasoning/peripherals/165')
-rw-r--r--results/classifier/deepseek-2/reasoning/peripherals/16511
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/reasoning/peripherals/165 b/results/classifier/deepseek-2/reasoning/peripherals/165
new file mode 100644
index 00000000..5f4ca257
--- /dev/null
+++ b/results/classifier/deepseek-2/reasoning/peripherals/165
@@ -0,0 +1,11 @@
+<think>
+Okay, I need to classify this bug report: "No evdev mouse passthrough with virtio-vga or kvm". The categories are mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
+
+The issue is about mouse passthrough not working. Mouse passthrough typically relates to how devices are handled in a virtualized environment. Since it's related to input devices (mouse), that points towards the "peripherals" category because peripherals usually include input/output devices like mice, keyboards, etc.
+
+Looking at the possible categories, 'device' could also be relevant, but 'peripherals' is more specific to input/output hardware. The bug mentions evdev, which is related to device events in Linux, and KVM is involved as a hypervisor. However, the core issue is about mouse passthrough not functioning, which falls under how peripherals are handled in the virtual environment.
+
+So, the most appropriate category here is 'peripherals'.
+</think>
+
+peripherals
\ No newline at end of file