blob: b2865350db2bc41def8863a842e4eca6b8cec47e (
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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
graphic: 0.917
device: 0.902
arm: 0.873
socket: 0.866
kernel: 0.841
performance: 0.840
network: 0.839
TCG: 0.837
PID: 0.831
hypervisor: 0.828
vnc: 0.820
risc-v: 0.814
ppc: 0.808
peripherals: 0.799
KVM: 0.775
VMM: 0.753
boot: 0.749
debug: 0.730
architecture: 0.723
permissions: 0.722
register: 0.722
i386: 0.641
files: 0.585
mistranslation: 0.523
x86: 0.513
user-level: 0.460
semantic: 0.425
assembly: 0.247
virtual: 0.196
xive: An extra '0x' prefix when printing hex values in the trace.
Description of problem:
The trace functions corresponding to the functions below print certain
parameters with a double "0x" prefix, i.e., with "0x0x".
- xive_source_esb_read
- xive_source_esb_write
- xive_tctx_tm_write
- xive_tctx_tm_read
Steps to reproduce:
1. Execute the command line on a terminal
2. Watch the terminal for the output.
Additional information:
Sample output:
xive_end_source_read END 0x0/0xf @0x0x1e0800
xive_source_esb_read @0x0x210c00 IRQ 0x10 val=0x0x1
xive_tctx_tm_read @0x0x10038 sz=1 val=0x0
xive_tctx_tm_write @0x0x10038 sz=1 val=0x80
xive_tctx_tm_read @0x0x10038 sz=1 val=0x80
xive_end_source_read END 0x0/0xf @0x0x1e0800
xive_source_esb_read @0x0x210c00 IRQ 0x10 val=0x0x1
xive_tctx_tm_read @0x0x10038 sz=1 val=0x0
xive_tctx_tm_write @0x0x10038 sz=1 val=0x80
xive_tctx_tm_read @0x0x10038 sz=1 val=0x80
The source lines at fault:
xive_source_esb_read(uint64_t addr, uint32_t srcno, uint64_t value) "@0x0x%"PRIx64" IRQ 0x%x val=0x0x%"PRIx64
xive_source_esb_write(uint64_t addr, uint32_t srcno, uint64_t value) "@0x0x%"PRIx64" IRQ 0x%x val=0x0x%"PRIx64
xive_tctx_tm_write(uint64_t offset, unsigned int size, uint64_t value) "@0x0x%"PRIx64" sz=%d val=0x%" PRIx64
xive_tctx_tm_read(uint64_t offset, unsigned int size, uint64_t value) "@0x0x%"PRIx64" sz=%d val=0x%" PRIx64
|