blob: 721f1e0a6c17d6c48d835170931e5323747ee45c (
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
28
29
30
31
32
33
34
35
36
37
|
graphic: 0.887
instruction: 0.841
device: 0.733
semantic: 0.632
other: 0.531
assembly: 0.512
vnc: 0.499
network: 0.436
socket: 0.432
KVM: 0.423
boot: 0.346
mistranslation: 0.215
PPC: `spr_write_xer` doesn't set flag bits in `cpu_xer`
Description of problem:
`spr_write_xer()` does not set the `ca`, `ov`, `so`, `ca32`, `ov32` etc. flag bits in the `cpu_xer` variable.
In fact it copies all bits from the source `GPR` and _excludes_ each flag bit.
This is not a problem for execution since `spr_read_xer()` gets the flag bits from `cpu_ca/ov/so...` and not from `cpu_xer`.
Nonetheless it is problem for tools which trace the execution in QEMU (e.g. https://github.com/BinaryAnalysisPlatform/qemu).
A fix would be to remove the `~` in https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L481
Steps to reproduce:
Haven't found out yet how to debug QEMU so the TCGv values can be investigated. But in general one need to:
- Execute a binary which executes something like:
```
r4 = 0xffffffffffffffff
mtxer r4
```
and check the `cpu_xer` value after the `xer` write.
Checking the debug logs (`in_asm,cpu`) doesn't work, since the `xer` value in the logs is not taken directly from `cpu_xer`.
Additional information:
Code ref: https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L480-L483
|