From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:57870)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1X9Iqd-0004X4-ER
	for qemu-devel@nongnu.org; Mon, 21 Jul 2014 15:02:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1X9IqS-0005jb-Ax
	for qemu-devel@nongnu.org; Mon, 21 Jul 2014 15:02:07 -0400
Received: from mail-pd0-x230.google.com ([2607:f8b0:400e:c02::230]:35765)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1X9IqS-0005hp-3Z
	for qemu-devel@nongnu.org; Mon, 21 Jul 2014 15:01:56 -0400
Received: by mail-pd0-f176.google.com with SMTP id y10so9693141pdj.21
	for <qemu-devel@nongnu.org>; Mon, 21 Jul 2014 12:01:55 -0700 (PDT)
Sender: Richard Henderson <rth7680@gmail.com>
Message-ID: <53CD6368.8050806@twiddle.net>
Date: Mon, 21 Jul 2014 09:00:56 -1000
From: Richard Henderson <rth@twiddle.net>
MIME-Version: 1.0
References: <20140718203004.20624.43575.malonedeb@wampee.canonical.com>
	<20140721104628.8786.41123.malone@soybean.canonical.com>
In-Reply-To: <20140721104628.8786.41123.malone@soybean.canonical.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Bug 1344320] Re: qemu-aarch64 cannot execute glibc
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bug 1344320 <1344320@bugs.launchpad.net>, qemu-devel@nongnu.org

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~