summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/none/1824778
blob: 361c961431dd320faf30ea0533d754b0570af60d (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
38
39
40
41
42
43
44
45
46
47
ppc: 0.672
architecture: 0.669
device: 0.493
semantic: 0.280
graphic: 0.275
VMM: 0.273
network: 0.264
PID: 0.236
files: 0.221
boot: 0.202
vnc: 0.194
register: 0.184
user-level: 0.177
arm: 0.158
socket: 0.151
permissions: 0.146
virtual: 0.145
TCG: 0.145
debug: 0.140
risc-v: 0.137
kernel: 0.136
mistranslation: 0.124
hypervisor: 0.110
peripherals: 0.110
performance: 0.083
x86: 0.076
i386: 0.057
KVM: 0.054
assembly: 0.052

PowerPC64: tlbivax does not work for addresses above 4G

The tlbivax instruction in QEMU does not work for address above 4G. The reason behind this is a simple 32bit trunction of an address.
Changing the argument ea from uint32_t to target_ulong for the function booke206_invalidate_ea_tlb() in target/ppc/mmu_helper.c solves the issue.

I did not reproduce this using Linux so I have no public example for reproducing it. However it's a pretty straight forward change.

Issue can be seen in all version of QEMU.


This is an automated cleanup. This bug report has been moved
to QEMU's new bug tracker on gitlab.com and thus gets marked
as 'expired' now. Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/52