From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Maciej W. Rozycki" Subject: Re: [PATCH v3 0/6] mips: system call table generation support Date: Thu, 6 Dec 2018 17:43:27 +0000 (GMT) Message-ID: References: <1543481016-18500-1-git-send-email-firoz.khan@linaro.org> <20181205063436.kzxgnvgexcgq572k@pburton-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23990824AbeLFRn11ifyA (ORCPT + 1 other); Thu, 6 Dec 2018 18:43:27 +0100 In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Joseph Myers Cc: Paul Burton , Firoz Khan , "open list:RALINK MIPS ARCHITECTURE" , Ralf Baechle , James Hogan , Greg Kroah-Hartman , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , y2038 Mailman List , Arnd Bergmann , Linux Kernel Mailing List , Linux-Arch , Deepa Dinamani , Marcin Juszkiewicz , libc-alpha@sourceware.org List-Id: linux-arch.vger.kernel.org On Thu, 6 Dec 2018, Joseph Myers wrote: > > So how are `SYS_' macros generated that land in ? > > By gen-syscall-h.awk, which generates #ifdef conditionals for each > possible __NR_* name (as listed in syscall-names.list in glibc). I seem to remember having to take extra care with how the three MIPS ABIs wire the syscalls to get it right in glibc, but I take it then this has been now addressed reliably enough for the glibc not to care how exactly has been arranged. Given my current level of involvement with the MIPS architecture I take your word for it and will not investigate it any further. Thanks for your input. Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eddie.linux-mips.org ([148.251.95.138]:43242 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725871AbeLFRna (ORCPT ); Thu, 6 Dec 2018 12:43:30 -0500 Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23990824AbeLFRn11ifyA (ORCPT + 1 other); Thu, 6 Dec 2018 18:43:27 +0100 Date: Thu, 6 Dec 2018 17:43:27 +0000 (GMT) From: "Maciej W. Rozycki" Subject: Re: [PATCH v3 0/6] mips: system call table generation support In-Reply-To: Message-ID: References: <1543481016-18500-1-git-send-email-firoz.khan@linaro.org> <20181205063436.kzxgnvgexcgq572k@pburton-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-arch-owner@vger.kernel.org List-ID: To: Joseph Myers Cc: Paul Burton , Firoz Khan , "open list:RALINK MIPS ARCHITECTURE" , Ralf Baechle , James Hogan , Greg Kroah-Hartman , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , y2038 Mailman List , Arnd Bergmann , Linux Kernel Mailing List , Linux-Arch , Deepa Dinamani , Marcin Juszkiewicz , libc-alpha@sourceware.org Message-ID: <20181206174327.qxXdRjQJ3fQvaL_NYMtbThwzKkS4KgayPXc12-qcrzw@z> On Thu, 6 Dec 2018, Joseph Myers wrote: > > So how are `SYS_' macros generated that land in ? > > By gen-syscall-h.awk, which generates #ifdef conditionals for each > possible __NR_* name (as listed in syscall-names.list in glibc). I seem to remember having to take extra care with how the three MIPS ABIs wire the syscalls to get it right in glibc, but I take it then this has been now addressed reliably enough for the glibc not to care how exactly has been arranged. Given my current level of involvement with the MIPS architecture I take your word for it and will not investigate it any further. Thanks for your input. Maciej