linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junichi Uekawa <dancer@netfort.gr.jp>
To: debian-devel@lists.debian.org, oprofile-list@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: A standard location to find 'vmlinux' to use for oprofile
Date: Sun, 15 Jan 2006 00:39:55 +0900	[thread overview]
Message-ID: <87oe2e7r90.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <87d5ja3y23.fsf@glaurung.internal.golden-gryphon.com>

Hi,
Cc'ing oprofile-list to see if anyone is interested in this topic.


> > I've been pondering on using kernel-package to generate debug
> > 'vmlinux' images which are used in tools like kernel crash dump
> > analysis tools and oprofile[1].
> 
> > Currently I'm running 'make vmlinux' after generating a package, but
> > it would be convenient if 'vmlinux' is included somewhere like
> > /usr/lib/debug/lib/modules/`uname -r`/vmlinux (which seems to be the
> > case with RedHat[2]).
> 
>         Support for this is already there -- if the config var
>  install_vmlinux is set, and your architectures make snippet defines
>  where to find the vmlinux, and where to install it, you are done.
> 
>         So, just provide data about kelfimagesrc and kelfimagedest for
>  files in /usr/share/kernel-package/rulesets/arches/, and then anyone
>  can set install_vmlinux to get the end result.

The remaining problem is that we don't really have a standard location
for 'vmlinux'.

For most cases, you can find the required file in
	 /lib/modules/$(uname -r)/build/vmlinux

but that's only available when you've built the kernel on that machine
and have the build tree lying around.

This is what oprofile currently does:
oprofile-0.9.1/gui/oprof_start_config.cpp:      /* Guess path to vmlinux based on kernel currently running. */
oprofile-0.9.1/gui/oprof_start_config.cpp:              string const vmlinux_path("/lib/modules/" + version
oprofile-0.9.1/gui/oprof_start_config.cpp:                                       + "/build/vmlinux");
oprofile-0.9.1/gui/oprof_start_config.cpp:              kernel_filename = vmlinux_path;


It would be nice if it's possible to obtain the location information
somewhere, in a distribution-agnostic manner.


regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project

           reply	other threads:[~2006-01-14 15:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87d5ja3y23.fsf@glaurung.internal.golden-gryphon.com>]

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=87oe2e7r90.dancerj%dancer@netfort.gr.jp \
    --to=dancer@netfort.gr.jp \
    --cc=debian-devel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).