From: Rob Landley <rob@landley.net>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Target-agnostic virtio?
Date: Mon, 29 Apr 2013 00:43:37 -0500 [thread overview]
Message-ID: <1367214217.18069.180@driftwood> (raw)
In-Reply-To: <CACXAS8BFcKcrHMiKVeaoNKFZSga7jS6e1odXEQ+cbzhBqLRA+Q@mail.gmail.com> (from atar4qemu@gmail.com on Sat Apr 27 15:00:06 2013)
On 04/27/2013 03:00:06 PM, Artyom Tarasenko wrote:
> > For a lot of the 64-bit targets, actual 64 bit userspace support is
> > strangely lacking. For ppc64 they say to use ppc32, and I've been
> told that
> > about sparc64 as well. I don't know if this is an optimization or a
> > requirement. I have a 32 bit image, I'd like to test the 64 bit
> codepaths as
> > well...
>
> I guess it's rather an optimisation. At least I saw BusyBox working
> under
> QEMU before the sparc v8plus was fixed.
If you mean http://busybox.net/downloads/binaries/busybox-sparc that's
a 32-bit binary output from the Aboriginal Linux build. (I try to
upload new ones each time Denys has a release, but I'm buried in todo
items and don't always get to it. Right now I need to clean up and
repost the inittmpfs patches for 3.9...)
Rob
next prev parent reply other threads:[~2013-04-29 14:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 0:52 [Qemu-devel] Target-agnostic virtio? Rob Landley
2013-03-26 1:24 ` Richard Henderson
2013-03-26 3:55 ` Rob Landley
2013-03-26 7:34 ` Artyom Tarasenko
2013-04-13 17:03 ` Rob Landley
2013-04-14 9:38 ` Artyom Tarasenko
2013-04-14 9:59 ` Mark Cave-Ayland
2013-04-14 19:49 ` Artyom Tarasenko
2013-04-15 17:21 ` Rob Landley
2013-04-17 2:15 ` Rob Landley
2013-04-20 10:36 ` Blue Swirl
2013-04-21 5:37 ` Rob Landley
2013-04-27 20:00 ` Artyom Tarasenko
2013-04-29 5:43 ` Rob Landley [this message]
2013-04-30 21:31 ` Artyom Tarasenko
2013-05-01 17:12 ` Rob Landley
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=1367214217.18069.180@driftwood \
--to=rob@landley.net \
--cc=atar4qemu@gmail.com \
--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).