[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Target-agnostic virtio?

From: Rob Landley
Subject: Re: [Qemu-devel] Target-agnostic virtio?
Date: Wed, 01 May 2013 12:12:05 -0500

On 04/30/2013 04:31:29 PM, Artyom Tarasenko wrote:
On Mon, Apr 29, 2013 at 7:43 AM, Rob Landley <address@hidden> wrote:
> 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.

No, I mean busybox-static_1.18.4-2_sparc64.deb from the older Debian
Meanwhile it's 1.20,
but I only experimented with 1.18. Back then it was definitely a pure
64 bit application:

let's see, wget the 1.20 version, dpkg-deb -X busybox-static* sparky,
strings sparky/bin/busybox | grep -i libc...

Statically linked against glibc 2.13. Still, good test for at least the application emulation side of things.

I hit the limits of platform support I could beat out of uClibc a few years back, and these days I'm poking at musl. (It doesn't support much yet, but it's a _lot_ easier to add new targets and klibc provides bsd-licensed templates for most of them.) I need to reproduce the existing uClibc targets I'm using so I can wean my project off of that package before worrying too much about new stuff though. :)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]