From: Richard Henderson <rth@twiddle.net>
To: Bug 1344320 <1344320@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1344320] Re: qemu-aarch64 cannot execute glibc
Date: Mon, 21 Jul 2014 09:00:56 -1000 [thread overview]
Message-ID: <53CD6368.8050806@twiddle.net> (raw)
In-Reply-To: <20140721104628.8786.41123.malone@soybean.canonical.com>
On 07/21/2014 12:46 AM, Peter Maydell wrote:
> Q: is this in a released glibc? The generic timers are strictly speaking
> optional, so this seems kind of bogus. Also looking at the glibc sources
> it never reads the counter frequency so what it is hoping to do with the
> timer values I have no idea.
>
It's trying to measure clock cycles required to perform the startup
relocations. E.g.
$ LD_DEBUG=statistics /bin/true
4224:
4224: runtime linker statistics:
4224: total startup time in dynamic loader: 558705 clock cycles
4224: time needed for relocation: 142093 clock cycles (25.4%)
4224: number of relocations: 2
4224: number of relocations from cache: 27
4224: number of relative relocations: 0
4224: time needed to load objects: 200809 clock cycles (35.9%)
4224:
4224: runtime linker statistics:
4224: final number of relocations: 4
4224: final number of relocations from cache: 27
r~
next prev parent reply other threads:[~2014-07-21 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 20:30 [Qemu-devel] [Bug 1344320] [NEW] qemu-aarch64 cannot execute glibc Andreas Schwab
2014-07-19 10:54 ` Peter Maydell
2014-07-21 18:55 ` Richard Henderson
2014-07-21 10:46 ` [Qemu-devel] [Bug 1344320] " Peter Maydell
2014-07-21 19:00 ` Richard Henderson [this message]
2014-07-21 20:37 ` Peter Maydell
2014-07-22 19:46 ` Richard Henderson
2014-07-22 22:22 ` Peter Maydell
2014-07-24 21:45 ` Richard Henderson
2014-07-25 8:54 ` Riku Voipio
2014-07-25 9:02 ` Ard Biesheuvel
2014-07-21 10:56 ` Peter Maydell
2014-08-29 11:48 ` Peter Maydell
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=53CD6368.8050806@twiddle.net \
--to=rth@twiddle.net \
--cc=1344320@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).