summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/graphic/2578
blob: 39d1dc9c3860e52d475a830ffce07f3fd7c7f440 (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
27
graphic: 0.890
instruction: 0.852
device: 0.814
KVM: 0.776
network: 0.664
socket: 0.644
vnc: 0.579
semantic: 0.512
other: 0.398
boot: 0.365
assembly: 0.347
mistranslation: 0.272

x86: exception during hardware interrupt pushes wrong error code
Description of problem:
Exceptions during IDT traversal push the wrong error code when triggered by a hardware interrupt.
The EXT bit in TCG mode is never set.  However, it works fine in KVM mode as hardware is generating the number.
Steps to reproduce:
1. load a short IDT e.g. with 64 entries
2. trigger a self IPI through the LAPIC with a vector 100
3. the pushed error code is 802 instead of 803.
Additional information:
It can be fixed in the lines `raise_exception_err(env, EXCP0D_GPF, intno * 8 + 2);` in `seg_helper.c` 
which must include the `is_hw` field when calculating the error number. Something like `intno * 8 + 2 + (is_hw != 0)` 
works here.

Nevertheless, all the other exception cases in the `do_interrupt_*` functions have to set the same bit as well.