Re: [Xen-devel] [PATCH v2 01/13] Export hypervisor symbols

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Mon, Sep 23, 2013 at 04:06:46PM -0400, Boris Ostrovsky wrote:
> On 09/23/2013 03:42 PM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Sep 20, 2013 at 05:42:00AM -0400, Boris Ostrovsky wrote:
> >
> >I think the title needs a prefix of say: "xen/platform_op:" or such.
> >
> >>Export Xen's symbols in format similar to Linux' /proc/kallsyms.
> >Which is?
> >
> >I see in Linux:
> >
> >000000000000bd58 D xen_cr3
> >...
> >000000000000e978 d soft_lockup_hrtimer_cnt
> >..
> >ffffffff8101cef0 T eager_fpu_init
> >ffffffff8101d010 t ptrace_triggered
> >
> >I know that the first column is the EIP (thought some of them seem to be
> >based on some offset). The last one is pretty obvious too.
> >
> >But the middle one:
> >konrad@phenom:~$ cat /proc/kallsyms  | awk '{print $2}' | sort | uniq
> >b
> >B
> >d
> >D
> >r
> >R
> >t
> >T
> >V
> >W
> >
> >Could you explain what those mean? And are they part of this?
> >Or does Xen not carry those?
> 
> These are symbol types, described in 'man nm'. For Xen we should

<sigh> I was doing 'man kallsyms' which of course would not give me that.


> only see 't' and 'T' which denote local or global text symbol.
> 
> So the format would be
> <address> <type> <symbol name>
> 
> In any case, this is not a comlpetely correct commit message, it
> really describes to v1 implementation. With v2 Xen will return these
> three values in a structure, which has nothing to do with *format*
> of how these symbols are presented. I'll re-phrase it.

Thank you. Sorry for the noise - it didn't occur for me to check 'nm' :-(

> 
> (And there other remnants of v1 in this patch that I just noticed,
> such as changes to xen/tools/symbols.c which are no longer needed)

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