Thanks, Ian. What I get from xen-syms-4.41 of do_hvm_op is 0xffff82d0801c988e and its size is 0x1e28, which is different with the trace log. So the result might not always be the truth?
> From: ian.campbell@xxxxxxxxxx
> To: quizy_jones@xxxxxxxxxxx; xen-users@xxxxxxxxxxxxx
> Date: Mon, 14 Dec 2015 09:59:35 +0000
> Subject: Re: [Xen-users] how to analyse xen call trace?
>
> On Sat, 2015-12-12 at 10:37 +0000, quizyjones wrote:
> > I got this while do operations on hypercalls, any idea on how to analysis
> > the error? Look at the sentence in bold, the virtual address of do_hvm_op
> > is 0xffff82d0801c988e in xen symbol files, while this log shows it
> > is ffff82d0801b7f68. What does '+0x1a98/0x1fd0' mean?
>
> It means the given RIP is 0x1a98 bytes into the function do_hvm_op(). The
> entire function is 0x1fd0 bytes (i.e. the RIP is about 4/5ths of the way
> through the function).
>
> Unless this annotation indicates the very start of end of the function I
> usually ignore it and instead use gdb to look at the actual rip using "list
> *0xffff82d0801b7f68" or "disas 0xffff82d0801b7f68".
>
> Others I know prefer addr2line.
>
> Ian.
>
> >
> > (XEN) Xen call trace:
> > (XEN) [<ffff82d080128132>] _write_unlock+0x22/0x40
> > (XEN) [<ffff82d0801dee6e>] paging_log_dirty_range+0x13e/0x180
> > (XEN) [<ffff82d08020d9f3>] hap_track_dirty_vram+0x393/0x4f0
> > (XEN) [<ffff82d08015f08d>] context_switch+0x13d/0xe80
> > (XEN) [<ffff82d08012a3bb>] add_entry+0x4b/0xb0
> > (XEN) [<ffff82d0801b7f68>] do_hvm_op+0x1a98/0x1fd0
> > (XEN) [<ffff82d080158635>] reprogram_timer+0x75/0xe0
> > (XEN) [<ffff82d080215908>] toggle_guest_mode+0x48/0xc0
> > (XEN) [<ffff82d080215a40>] do_iret+0xc0/0x1a0
> > (XEN) [<ffff82d08021aef9>] syscall_enter+0xa9/0xae
> > (XEN)
> > (XEN)
> > (XEN) ****************************************
> > (XEN) Panic on CPU 0:
> > (XEN) FATAL TRAP: vector = 6 (invalid opcode)
> > (XEN) ****************************************
> > (XEN)
> > (XEN) Reboot in five seconds...
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users
