From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: acme@infradead.org, linux-kernel@vger.kernel.org,
fweisbec@gmail.com, efault@gmx.de, a.p.zijlstra@chello.nl,
paulus@samba.org
Subject: Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing
Date: Tue, 16 Mar 2010 02:51:34 -0700 (PDT) [thread overview]
Message-ID: <20100316.025134.196872789.davem@davemloft.net> (raw)
In-Reply-To: <20100316094611.GG7961@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 16 Mar 2010 10:46:11 +0100
> i'd really like that to happen - i.e. if we had the kernel (and modules) image
> exposed as a (almost-)standard ELF object via /sys or so.
>
> We already have some aspects of that, via /sys/kernel/notes, but it should be
> done for real. That would also make build-id support less of a hack.
>
> ( I'd not include CFI debuginfo in there though - that would be way too large.
> More compressed debuginfo could be included perhaps. )
That's interesting and useful, but wouldn't help my case as the images
I'm usually booting are completely stripped.
That's why I end up with "[kernel.kallsyms]" for kernel profiling :-)
next prev parent reply other threads:[~2010-03-16 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 14:46 [PATCH 1/2] perf record: Enable the enable_on_exec flag if record forks the target Arnaldo Carvalho de Melo
2010-03-15 14:46 ` [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing Arnaldo Carvalho de Melo
2010-03-15 18:55 ` David Miller
2010-03-15 19:21 ` Arnaldo Carvalho de Melo
2010-03-15 19:26 ` David Miller
2010-03-16 9:46 ` Ingo Molnar
2010-03-16 9:51 ` David Miller [this message]
2010-03-16 9:55 ` Ingo Molnar
2010-03-16 9:58 ` David Miller
2010-03-15 15:15 ` [tip:perf/core] perf record: Enable the enable_on_exec flag if record forks the target tip-bot for Eric B Munson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100316.025134.196872789.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox