[Top][All Lists]

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

Re: [Qemu-devel] [PATCH] user-exec.c: fix build on NetBSD/sparc64 and Ne

From: Tobias Nygren
Subject: Re: [Qemu-devel] [PATCH] user-exec.c: fix build on NetBSD/sparc64 and NetBSD/arm
Date: Sun, 8 Mar 2015 15:59:23 +0100

On Sun, 8 Mar 2015 21:53:30 +0900
Peter Maydell <address@hidden> wrote:

> On 8 March 2015 at 21:37, Tobias Nygren <address@hidden> wrote:
> > On Sun, 8 Mar 2015 19:27:27 +0900
> > Peter Maydell <address@hidden> wrote:
> >> Does NetBSD have a big stack of out-of-tree patches for QEMU,
> >> or do you run basically stock upstream QEMU?
> >
> > Hi, it is more or less stock except for this patch.
> Cool. (I know the FreeBSD folk have a pretty large set
> of user-mode emulation changes which we've unfortunately
> not been able to get upstream yet since there's a lot of
> cleanup work required.)
> Does the user-emulation work for running random
> binaries, or are there known limitations to what
> guest/host architectures work well? (I have some
> BSD VMs which I was using for compile testing of
> the bsd-user code a while back, but I forget what
> results I was seeing with which BSD variant...)

I don't know much more than that developers are actively using it to
test their changes on some architectures. It works well enough for them
to get their job done, I suppose.

Standalone static binaries and basic syscall emulation seem to work OK.
There is a problem with ps_strings / argv[0] being NULL in crt0.o.
(looks like it would not be hard to fix)

> > There
> > are three other small patches that add parenthesis in a few
> > places to work around a conflict with system macros when
> > -fstack-protector is enabled but I'm not confident
> > those are suitable for upstreaming.
> If they're small you might as well post them here anyway;
> we may be able to suggest a better fix or perhaps they'll
> be OK to apply upstream anyway.

Actually looking further this has been properly fixed in the base system
and only affects the old 5.x release which is due to be desupported
when 7.0 is released, so I wouldn't worry about it.


reply via email to

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