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

2020-02-11 Thread Laurent Vivier
Thank you Peter, I will address you comments and send a new version of the series. Laurent Le 11/02/2020 à 18:05, Peter Maydell a écrit : > On Tue, 4 Feb 2020 at 17:11, Laurent Vivier wrote: >> >> Some RT signals can be in use by glibc, >> it's why SIGRTMIN (34) is generally greater than __SIGR

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

2020-02-11 Thread Peter Maydell
On Tue, 4 Feb 2020 at 17:11, Laurent Vivier wrote: > > Some RT signals can be in use by glibc, > it's why SIGRTMIN (34) is generally greater than __SIGRTMIN (32). > > So SIGRTMIN cannot be mapped to TARGET_SIGRTMIN. > > Instead of swapping only SIGRTMIN and SIGRTMAX, map all the > range [TARGET_SI

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

2020-02-05 Thread Taylor Simpson
> ; milos.stojano...@rt-rk.com; Marlies Ruck > > Subject: [PATCH v2 4/4] linux-user: fix use of SIGRTMIN > > - > CAUTION: This email o

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

2020-02-04 Thread Laurent Vivier
Some RT signals can be in use by glibc, it's why SIGRTMIN (34) is generally greater than __SIGRTMIN (32). So SIGRTMIN cannot be mapped to TARGET_SIGRTMIN. Instead of swapping only SIGRTMIN and SIGRTMAX, map all the range [TARGET_SIGRTMIN ... TARGET_SIGRTMAX - X] to [__SIGRTMIN + X ... SIGRT