Re: [PATCH 0/4] linux-user: fix use of SIGRTMIN

2020-02-04 Thread Josh Kunz
On Tue, Feb 4, 2020 at 3:55 AM Laurent Vivier wrote: > We should add signal 63 here, but it's becoming not very clean. https://golang.org/issue/33746 has some discussion of the issue. The Go maintainers wanted to clean this up rather than just adding 63. The patch is on ice right now because it w

Re: [PATCH 0/4] linux-user: fix use of SIGRTMIN

2020-02-04 Thread Laurent Vivier
Le 04/02/2020 à 01:03, Josh Kunz a écrit : > On Sat, Feb 1, 2020 at 4:27 AM Laurent Vivier wrote: >> This has been tested with Go (golang 1.10.1 linux/arm64, bionic) on x86_64 >> fedora 31. We can avoid the failure in this case allowing the unsupported >> signals when we don't provide the "act" pa

Re: [PATCH 0/4] linux-user: fix use of SIGRTMIN

2020-02-03 Thread Josh Kunz
On Sat, Feb 1, 2020 at 4:27 AM Laurent Vivier wrote: > This has been tested with Go (golang 1.10.1 linux/arm64, bionic) on x86_64 > fedora 31. We can avoid the failure in this case allowing the unsupported > signals when we don't provide the "act" parameters to sigaction, only the > "oldact" one.

RE: [PATCH 0/4] linux-user: fix use of SIGRTMIN

2020-02-03 Thread Taylor Simpson
FWIW, this removes the need for the target-specific code for Hexagon in signal.c. Thanks, Taylor PS Stay tuned for a Hexagon target patch series once this is merged. > -Original Message- > From: Laurent Vivier > Sent: Saturday, February 1, 2020 6:28 AM > To: qemu-devel@nongnu.org > Cc