Hi All
I am currently working on DomU kernel with some passthrough-drivers / hacking based on ARM A53 platform.
There are some time that the DomU kernel is ruined too early before xenconsole could connect to start emit error log.
I will need the whole stack dump / earlyprintk log to check what is going on at boot time.
Here are my questions and I will really appreciate if someone could help :)
1. Is earlyprintk works on DomU?? I tried to add following config but it doesn’t seems to work.
extra = "earlyprintk=xenboot console=hvc0 debug"
2. Is there existing console logging system for DomU, recording all the console log (basically kernel) to Dom0 file system?
3. I use the tool xenctx, trying to dump vcpu info for checking error status. But it seems stack dump isn’t working which I would like
to use it for checking the call-trace for finding out the point DomU is getting trouble. The output on my board is like following :
root@buildroot-Dom0:$ /usr/local/lib/xen/bin/xenctx -S -a -s System.map 5
PC: ffffffc0102cdf48 __delay+0x28
LR: ffffffc0102cdf7c
ELR_EL1: 0000000000000000
CPSR: 80000045
SPSR_EL1: 00000000
SP_EL0: 0000000000000000
SP_EL1: ffffffc010813e40
x0: 0000000000000199 x1: 0000011bb3021e7f x2: 0000011bb3021df8
x3: 0000000000000003 x4: 000000000000001d x5: 0000000000000006
x6: ffffffc010879149 x7: 000000000000001e x8: 6f6d656d20666f20
x9: ffffffc010813bc0 x10: 000000000000001d x11: ffffffc010824000
x12: 0101010101010101 x13: 0000000000000028 x14: 0ffffffffffffffe
x15: ffffffc01089fe48 x16: 0000000000000000 x17: 00000000ffffffff
x18: 00000000000000ad x19: 000000000000002a x20: 00000000b111c644
x21: 00000000b111c6a8 x22: ffffffc010875000 x23: 0000000000000001
x24: 0000000080000200 x25: ffffffc01081e000 x26: 00000000408cd000
x27: ffffffc010081220 x28: 0000000000000000 x29: ffffffc010813e40
SCTLR: 34d5d91d
TTBCR: 00000032b5193519
TTBR0: 000000004ffff000
TTBR1: 00000000408cd000
Thanks
Tom
