Re: [Xen-devel] Which Xen binary can I use?

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 11.09.17 at 05:20, <nickeysgo@xxxxxxxxx> wrote:
> Hi.
> I'm working on a scheduling code by which I received a patch regarding
> credit scheduler from my professor.
> I have had some troubles during that work and I need to make the Xen binary
> with 'debug=y' option.
> But there was a kernel panic caused by the debugging code triggered by
> 'debug=y' option during booting process(of dom0):
> 
> 
> (XEN) ----[ Xen-4.5.0  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    7
> (XEN) RIP:    e008:[<ffff82d08012ba6c>] vcpu_migrate+0x1bd/0x374
> (XEN) RFLAGS: 0000000000010096   CONTEXT: hypervisor
> (XEN) rax: ffff82d080413320   rbx: ffff830461c3e068   rcx: ffff82d080428e60
> (XEN) rdx: 0000000000201da0   rsi: ffff830086d2f000   rdi: ffff82d080280bc0
> (XEN) rbp: ffff83045e77fe48   rsp: ffff83045e77fdd8   r8:  0000000000000007
> (XEN) r9:  00000000deadbeef   r10: ffff82d08024d870   r11: 0000000000000246
> (XEN) r12: ffff830461c3e068   r13: 0000000000000007   r14: ffff82d080428e60
> (XEN) r15: ffff830461c3e068   cr0: 0000000080050033   cr4: 00000000003526f0
> (XEN) cr3: 0000000459c0c000   cr2: ffff82d081422020
> (XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff83045e77fdd8:
> (XEN)    ffff82d080428e60 ffff82d080428e60 ffff83045e77fdf8 ffff82d080428e60
> (XEN)    ffff83045e77fe00 ffff830086d2f000 00201da000000086 0000000000000246
> (XEN)    ffff82d08012e0c6 ffff830086d2f000 ffff830461c3e068 ffff82d080428e60
> (XEN)    ffff82d080413320 ffff83045e78a000 ffff83045e77fe78 ffff82d08012be23
> (XEN)    0000000000000007 ffff830086d2f000 0000000000000000 0000000000000000
> (XEN)    ffff83045e77fef8 ffff82d080107052 ffffffff00000000 0000000000000008
> (XEN)    0000000000a0fb00 0000000000000000 ffffffffffffffff 0000000001000c02
> (XEN)    ffff83045e77fe32 ffff82d080196da9 0f00000000000001 ffff830086d2f000
> (XEN)    ffff880456bcc4c0 0000000000000007 0000000000000000 0000000000000000
> (XEN)    00007cfba18800c7 ffff82d080234d9b ffffffff8100130a 0000000000000018
> (XEN)    0000000000000000 0000000000000002 0000000001000c02 ffff880450b43e3c
> (XEN)    ffff880450b43e88 ffff880456bcc4c0 0000000000000246 0000000000000004
> (XEN)    0000000000000000 0000000000000004 0000000000000018 ffffffff8100130a
> (XEN)    0000000000000000 0000000000000007 0000000000000007 0001010000000000
> (XEN)    ffffffff8100130a 000000000000e033 0000000000000246 ffff880450b43e70
> (XEN)    000000000000e02b 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000007 ffff830086d2f000 00000033e1815200
> (XEN)    0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff82d08012ba6c>] vcpu_migrate+0x1bd/0x374
> (XEN)    [<ffff82d08012be23>] vcpu_force_reschedule+0x9e/0xa7
> (XEN)    [<ffff82d080107052>] do_vcpu_op+0x2e7/0x69d
> (XEN)    [<ffff82d080234d9b>] syscall_enter+0xeb/0x145
> (XEN)
> (XEN) Pagetable walk from ffff82d081422020:
> (XEN)  L4[0x105] = 0000000086092063 ffffffffffffffff
> (XEN)  L3[0x142] = 000000008608f063 ffffffffffffffff
> (XEN)  L2[0x00a] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 7:
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff82d081422020
> (XEN) ****************************************
> 
> Even if I turned on the 'debug=y' option, I could not get accurate
> information like with 'debug=n' option; I get only linear
> address(ffff82d081422020).

As was pointed out to you by Dario, you won't get anything better.
From there on it is a human (i.e. your in this case) job to do the
necessary further analysis.

> So, I want to use a dis-assembly utility like 'addr2line' or 'objdump',
> which binaries can I use as input to the utilities?

xen-syms or xen.efi, depending on how you boot.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel