summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/hypervisor/1908781
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:34:26 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:35:44 +0000
commit25f8033d556aa17afaea4a5196ea7a69fe248320 (patch)
tree0f056db167683be54ea1e5e72d29d6069af55e7d /results/classifier/deepseek-2-tmp/output/hypervisor/1908781
parent8e6da29e4ee5fc14bc1cc816a24f21271f14090d (diff)
downloadqemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.tar.gz
qemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.zip
add new temporary deepseek-r1:14b results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1908781')
-rw-r--r--results/classifier/deepseek-2-tmp/output/hypervisor/190878110
1 files changed, 10 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1908781 b/results/classifier/deepseek-2-tmp/output/hypervisor/1908781
new file mode 100644
index 000000000..bb5d71ced
--- /dev/null
+++ b/results/classifier/deepseek-2-tmp/output/hypervisor/1908781
@@ -0,0 +1,10 @@
+
+x86-64 not faulting when CS.L = 1 and CS.D = 1
+
+In a UEFI application I accidentally created a code segment descriptor where both the L and D bits were 1. This is supposed to generate a GP fault (e.g. see page 2942 of https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf). When running with KVM a fault did indeed occur, but when not specifying any acceleration, no fault occurred.
+
+Let me know if you need me to develop a minimum example to debug from. At the moment it's all part of a slightly more complicated bit of code.
+
+Version: 5.2.0 (compiled from source)
+Command line options: -smp cores=4 -m 8192 (plus whatever uefi-run adds to plug in OVMF and my UEFI application).
+Environment: Ubuntu 20.04 on Ryzen 3700X
\ No newline at end of file