summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1078892
blob: c7ed95ef203f305e74e9902760ff965e09c2e1ac (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
device: 0.781
boot: 0.714
graphic: 0.701
vnc: 0.544
semantic: 0.510
other: 0.462
files: 0.395
network: 0.376
socket: 0.350
performance: 0.290
permissions: 0.287
PID: 0.253
debug: 0.231
KVM: 0.114

qemu doesn't general protection fault if there are reserved bits set in page-directory-pointer table entries

While working on implementing 32-bit PAE mode in a custom operating system, which I was testing in QEMU, I noticed that my OS worked correctly, but resulted in a general protection fault when booted on VMware, VirtualBox, or bochs.

According to the Intel Architecture Manual, Volume 3A, Section 4.4.1 "PDPTE Registers", "If any of the PDPTEs sets both the P flag (bit 0) and any reserved bit, the MOV to CR instruction causes a general-protection exception (#GP(0)) and the PDPTEs are not loaded." QEMU does not emulate this behavior.

Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?

[Expired for QEMU because there has been no activity for 60 days.]