From: Peter Maydell <peter.maydell@linaro.org>
To: Roger <roger.junk.email@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Configuring QEMU to translate x86 instructions to native ARM instructions
Date: Tue, 6 Mar 2012 16:14:04 +0000 [thread overview]
Message-ID: <CAFEAcA85Hmh2B_OzRDDPfRyKo1LT5GcVm3fdPm_j24PUmncaww@mail.gmail.com> (raw)
In-Reply-To: <6C6D562C-2B45-4187-9A4E-E55801BDA7F2@gmail.com>
On 6 March 2012 16:09, Roger <roger.junk.email@gmail.com> wrote:
> I will try the --cross-prefix option. I have a feeling this
> will do it. I know that the prologue is being initialized with
> the i386 target backend
> I'll also try the --cpu option recommended by the previous poster.
Yes, this should force the host CPU detection correctly, but
really it ought to be able to autodetect it, at least in current
versions of QEMU. This might possibly have been broken in 0.15,
I suppose.
-- PMM
next prev parent reply other threads:[~2012-03-06 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 5:11 [Qemu-devel] Configuring QEMU to translate x86 instructions to native ARM instructions Roger Tagged
2012-03-06 15:54 ` Peter Maydell
2012-03-06 16:09 ` Roger
2012-03-06 16:14 ` Peter Maydell [this message]
2012-03-07 14:26 ` Roger
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=CAFEAcA85Hmh2B_OzRDDPfRyKo1LT5GcVm3fdPm_j24PUmncaww@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=roger.junk.email@gmail.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).