Hi, Arnd, On Thu, Jul 8, 2021 at 9:30 PM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > On Thu, Jul 8, 2021 at 3:04 PM Huacai Chen <chenhuacai@xxxxxxxxx> wrote: > > On Tue, Jul 6, 2021 at 6:17 PM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > > On Tue, Jul 6, 2021 at 6:18 AM Huacai Chen <chenhuacai@xxxxxxxxxxx> wrote: > > > > + > > > > +#ifndef _NSIG > > > > +#define _NSIG 128 > > > > +#endif > > > > > > Everything else uses 64 here, except for MIPS. > > > > Once before we also wanted to use 64, but we also want to use LBT to > > execute X86/MIPS/ARM binaries, so we chose the largest value (128). > > Some applications, such as sighold02 in LTP, will fail if _NSIG is not > > big enough. > > Have you tried separating the in-kernel _NSIG from the number used > in the loongarch ABI? This may require a few changes to architecture > independent signal handling code, but I think it would be a cleaner > solution, and make it easier to port existing software without having > to special-case loongarch along with mips. Jun Yi (yili0568@xxxxxxxxx) is my colleague who develops LBT software, he has some questions about how to "separate the in-kernel _NSIG from the number used in the LoongArch ABI". Huacai > > Arnd
