public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: offline elfutils processing committed
Date: Wed, 01 Nov 2006 20:37:00 -0000	[thread overview]
Message-ID: <20061101200336.7B0A8180053@magilla.sf.frob.com> (raw)
In-Reply-To: Frank Ch. Eigler's message of  Tuesday, 31 October 2006 21:13:00 -0500 <20061101021300.GV4978@redhat.com>

Go team!  When I added the elfutils support for relocatability in August of
last year, I was really hoping someone would start testing it one day. ;-)

Is "somewhat longer" not an understatement?  When I use elfutils'
tests/dwflmodtest with -K (offline kernel, 1389 modules) vs -k (running
kernel, 64 modules) it takes about 17 times longer (mostly i/o).  Note that
dwfl_linux_kernel_report_offline lets you supply a predicate to exclude
uninteresting modules, which is the only way I've thought of to reduce the
DWARF-loading overhead (without changing the way we install it).

You didn't change dwflpp::emit_address, which is used for things like
$global_var addresses.  That needs to emit references to your run-time
section addresses too.


Thanks,
Roland

  reply	other threads:[~2006-11-01 20:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  4:48 Frank Ch. Eigler
2006-11-01 20:37 ` Roland McGrath [this message]
2006-11-04  3:29   ` Frank Ch. Eigler
2006-11-04  4:05     ` Roland McGrath
2006-11-04 14:27       ` Frank Ch. Eigler
2006-11-06 20:55     ` Martin Hunt
2006-11-06 21:18       ` Frank Ch. Eigler
2006-11-06 21:52         ` Martin Hunt
2006-11-06 22:15           ` Frank Ch. Eigler
2006-11-01 22:22 Stone, Joshua I
2006-11-01 22:57 ` Frank Ch. Eigler
2006-11-02 16:42 Stone, Joshua I
2006-11-06 22:41 Stone, Joshua I
2006-11-07  4:37 ` Roland McGrath
2006-11-07  6:36 ` Martin Hunt
2006-11-07 15:13   ` Frank Ch. Eigler
2006-11-07 15:43     ` Martin Hunt
2006-11-07 16:17       ` Frank Ch. Eigler
2006-11-07 16:39         ` Martin Hunt
2006-11-08  1:26           ` Frank Ch. Eigler

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=20061101200336.7B0A8180053@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=fche@redhat.com \
    --cc=systemtap@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).