From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Matz <matz@suse.de>, Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] arm64: Set source for ret instruction correctly.
Date: Tue, 24 Dec 2013 08:45:32 +0000 [thread overview]
Message-ID: <20131224084532.GB32597@redhat.com> (raw)
In-Reply-To: <CAFEAcA-MGw+o7KV=6BQwFTkvw3-wCk5ObcgQY3JqYKTpm-C-iw@mail.gmail.com>
On Mon, Dec 23, 2013 at 10:17:15PM +0000, Peter Maydell wrote:
> FWIW mainline's handling of this insn doesn't have this bug.
OT: Is there a clear explanation of the various aarch64 trees?
I noticed that upstream qemu has some files like target-arm/
translate-a64.c, but it didn't (and still doesn't) appear to work:
+ ./configure '--target-list=arm64-linux-user i386-softmmu x86_64-softmmu arm-softmmu ppc-softmmu ppc64-softmmu' '--extra-ldflags=-pie -Wl,-z,relro -Wl,-z,now' '--extra-cflags=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -fPIE -DPIE' --disable-werror --disable-xen --enable-kvm --enable-tpm
ERROR: Unknown target name 'arm64-linux-user'
I found the SuSE tree and it works, but the code is quite different
from the upstream tree.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2013-12-24 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 22:00 [Qemu-devel] [PATCH] arm64: Set source for ret instruction correctly Richard W.M. Jones
2013-12-23 22:17 ` Peter Maydell
2013-12-24 8:45 ` Richard W.M. Jones [this message]
2013-12-24 10:33 ` 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=20131224084532.GB32597@redhat.com \
--to=rjones@redhat.com \
--cc=agraf@suse.de \
--cc=matz@suse.de \
--cc=peter.maydell@linaro.org \
--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).