[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091231103609.GE2384@ghostprotocols.net>
Date: Thu, 31 Dec 2009 08:36:09 -0200
From: Arnaldo Carvalho de Melo <acme@...radead.org>
To: Xiao Guangrong <xiaoguangrong@...fujitsu.com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
James Bottomley <James.Bottomley@...e.de>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Paul Mackerras <paulus@...ba.org>,
"Frank Ch. Eigler" <fche@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] x86: record relocation offset
Em Thu, Dec 31, 2009 at 11:00:00AM +0800, Xiao Guangrong escreveu:
> Arnaldo Carvalho de Melo wrote:
> > Conclusion: at 'perf record' time store the address of a well know
> > symbol (_text) into the perf.data header. Later, at perf report time, if
> > using a vmlinux file, calculate the relocation by subtracting the same
> > well known symbol from the one stored in the header.
> > So no need for ioctl or boot stuff.
> I'm little confused, how to get the load symbol address?
> It's not a good way, if you get it from '/proc/kallsyms', we can't assume kernel
> has this file.
Well, then its just a matter of exposing _text as
/sys/kernel/sections/.text, as we already have for modules:
[acme@ana linux-2.6-tip]$ cat /sys/module/ipv6/sections/.text
0xfa0c2000
Which matches
nf_conntrack_ipv6 17548 2 - Live 0xfa147000
ipv6 239420 32 ip6t_REJECT,nf_conntrack_ipv6, Live 0xfa0c2000
[acme@ana linux-2.6-tip]$
But even as a quick transational assist, we can look at kallsyms at
'perf record' time.
> > I'll do that tomorrow, if Xiao doesn't beats me to it :-)
> Of course, please do if you have a better way :-)
I meant, if you didn't write the patch first, while I was sleeping :-)
I'll work on it today after some coffee and errands.
Best Regards,
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists