Re: [Qemu-discuss] golang on linux-user

2016-03-04 Thread Peter Maydell
On 4 March 2016 at 05:14, Jakob Bohm wrote: > There are lots of possibilities once you don't treat glibc as a > black box, If you don't treat glibc as a black box then you become very vulnerable to being broken when details of its implementation change. (Also it means you may no longer work with

Re: [Qemu-discuss] golang on linux-user

2016-03-03 Thread Jakob Bohm
On 01/03/2016 14:08, Peter Maydell wrote: On 1 March 2016 at 13:00, Jakob Bohm wrote: As an alternative, could it be useful to look beyond the current glibc code and see if there is a way for qemu-user to provide the full set of Linux syscall provided facilities (including signals and calls), w

Re: [Qemu-discuss] golang on linux-user

2016-03-02 Thread Hunter Laux
Would it be possible to multiplex 64 by using sigqueue? Just use si_value as the signal number when multiplexing. Then you wouldn't have to keep taking away signal numbers from runtimes and you break sigqueue for one signal number. Just return an error and set EINVAL if a program calls sigaction

Re: [Qemu-discuss] golang on linux-user

2016-03-01 Thread Peter Maydell
On 1 March 2016 at 13:00, Jakob Bohm wrote: > As an alternative, could it be useful to look beyond the current > glibc code and see if there is a way for qemu-user to provide the > full set of Linux syscall provided facilities (including signals > and calls), without having to reserve some for its

Re: [Qemu-discuss] golang on linux-user

2016-03-01 Thread Jakob Bohm
On 01/03/2016 12:37, Peter Maydell wrote: On 1 March 2016 at 09:38, Hunter Laux wrote: I was having trouble running golang on linux-user with an aarch64 target. It turns out that snappy is written in Go. When I tried the xenial aarch64 preinstall image in qemu, Snappy was broken. For some rea

Re: [Qemu-discuss] golang on linux-user

2016-03-01 Thread Peter Maydell
On 1 March 2016 at 09:38, Hunter Laux wrote: > I was having trouble running golang on linux-user with an aarch64 target. > > It turns out that snappy is written in Go. When I tried the xenial aarch64 > preinstall image in qemu, Snappy was broken. > > For some reason, it calls sigaction on all the

[Qemu-discuss] golang on linux-user

2016-03-01 Thread Hunter Laux
I was having trouble running golang on linux-user with an aarch64 target. It turns out that snappy is written in Go. When I tried the xenial aarch64 preinstall image in qemu, Snappy was broken. For some reason, it calls sigaction on all the signals. I noticed do_sigaction in linux-user/signal.c