* David Miller <davem@davemloft.net> wrote:

quoted text
> 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.

/me too

quoted text
> 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
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/