[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/4] linux-user: fix use of SIGRTMIN
From: |
Laurent Vivier |
Subject: |
Re: [PATCH v2 0/4] linux-user: fix use of SIGRTMIN |
Date: |
Tue, 11 Feb 2020 16:40:22 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 |
Peter,
do you have any comment on this way to fix the SIGRTMIN problem we have
now for years?
Thanks,
Laurent
Le 04/02/2020 à 18:10, Laurent Vivier a écrit :
> This series fixes the problem of the first real-time signals already
> in use by the glibc that are not available for the target glibc.
>
> Instead of reverting the first and last real-time signals we rely on
> the value provided by the glibc (SIGRTMIN) to know the first available
> signal and we map all the signals from this value to SIGRTMAX on top
> of TARGET_SIGRTMIN. So the consequence is we have less available signals
> in the target (generally 2) but all seems fine as at least 30 signals are
> still available.
>
> 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. I have also run the LTP suite with several target and debian
> based distros.
>
> v2: tested with golang 1.12.10 linux/arm64, eoan)
> Ignore unsupported signals rather than returning an error
> replace i, j by target_sig, host_sig
>
> Laurent Vivier (4):
> linux-user: add missing TARGET_SIGRTMIN for hppa
> linux-user: cleanup signal.c
> linux-user: fix TARGET_NSIG and _NSIG uses
> linux-user: fix use of SIGRTMIN
>
> linux-user/hppa/target_signal.h | 1 +
> linux-user/signal.c | 117 +++++++++++++++++++++++---------
> linux-user/trace-events | 3 +
> 3 files changed, 89 insertions(+), 32 deletions(-)
>