[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100316095523.GJ7961@elte.hu>
Date: Tue, 16 Mar 2010 10:55:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: David Miller <davem@...emloft.net>
Cc: acme@...radead.org, linux-kernel@...r.kernel.org,
fweisbec@...il.com, efault@....de, a.p.zijlstra@...llo.nl,
paulus@...ba.org
Subject: Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is
missing
* David Miller <davem@...emloft.net> wrote:
> From: Ingo Molnar <mingo@...e.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.
/me too
> That's why I end up with "[kernel.kallsyms]" for kernel profiling :-)
The kernel image itself is still present in RAM, obviously. So are the symbols
(packed for kallsyms).
So exposing a virtual ELF image via /sys (or /proc/kernel.so) wouldnt take up
much more RAM and would be rather useful, right?
Ingo
--
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