From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Richard Earnshaw <rearnsha@arm.com>
Subject: Re: [Qemu-devel] [Bug 1344320] Re: qemu-aarch64 cannot execute glibc
Date: Thu, 24 Jul 2014 11:45:37 -1000 [thread overview]
Message-ID: <53D17E81.8060003@twiddle.net> (raw)
In-Reply-To: <CAFEAcA96VX8Zfc-7bi4WiC=PcMJbLvJJDmbeCinm8wRQ59cZAQ@mail.gmail.com>
On 07/22/2014 12:22 PM, Peter Maydell wrote:
> In any case the kernel guys say you can't guarantee they
> exist unless you get them to define an ELF hwcap for
> "timers exist and have a sane value in the 'what frequency
> are they' register". So this is a glibc bug and I'm
> not fixing QEMU...
There seems to be a bit of confusion in the manual:
In the Preface:
# Chapter D7 The Generic Timer
# Read this for a description of an implementation of the ARM Generic Timer,
that is an extension to
# an ARMv8 PE implementation.
Section A1.3.3:
# The System registers comprise:
# General system control registers.
# Debug registers.
# Generic Timer registers.
# Optionally, Performance Monitor registers.
# Optionally, Trace registers.
# Optionally, Generic Interrupt Controller (GIC) CPU interface registers.
Note that there are 3 sections marked "optional", but not including the timer.
So which is true: typo here in A1.3.3 or are the GT registers required to exist?
r~
next prev parent reply other threads:[~2014-07-24 21:46 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
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 [this message]
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=53D17E81.8060003@twiddle.net \
--to=rth@twiddle.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rearnsha@arm.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 NNTP newsgroup(s).