Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5282974imu; Wed, 19 Dec 2018 08:30:53 -0800 (PST) X-Google-Smtp-Source: AFSGD/WxTN1QUHRdY0ZhHnrG7A4/EJBxkd6qbkSYSkTrDzql+S4Aq0viV6SteRq6N8lMVDB2VC5i X-Received: by 2002:a17:902:ab92:: with SMTP id f18mr20113391plr.221.1545237053527; Wed, 19 Dec 2018 08:30:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545237053; cv=none; d=google.com; s=arc-20160816; b=royRckv0cU0Nxw2kqR9q9OLBmDQGCQa58Q/1UnGr0O68BAxiPRtffz91Md0LoWoq+x lEv/8pg+sz0wNNHe6YP/8SxUth7YwDIhw+qfC+I6OHdSWDlXwrAmB3/iSejT5A0KkVWY QnLs6qmj+r+QwhfEPsxnVnhBqYpeRaa2C0G5Wa1Bt0g0qdqE+9XHf+U6ASs7pijmIpyu KLJSn5pS/+VMYgzTpbOXanTWRL5VJKzFkKfouFIOwCA3G7yo/aDZOrSdCagthocZubjv iDU69MZ1kTB22YnsfNZ/nvseNZO7ElJBNFrl+jbx65jeGuT2t7TmaAjsmFBXnGI9Ytts Cquw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=L9Oe0ayTRjWuO0bO25VljJGJZxyDQt7qiLMrAfR62L4=; b=y8ECFegj6DY74uzuS/NMcVGonaw4LCwcXZFQHrrbo1J1V8GbsurMLwWjtEdzKkK+ob cng0KYDf56QI5UFOJSImFg652llMQL7Zq259Ljb/7wQrzDASmyW773AvQJFKXAWRtUoK ziPUOXUsl5Dt3fkXYgd6erovmQGiHex7luqCJ4F1yfv4zw8ml7CDfufqoVEKwteaetlr 3zo4MkIJoOPT4qi5LgXAdLfBj8JJR8hlqAhvWscbk2ByWxeHYLMcf3LTFTHloxnzOjF2 iTT9t5dmnYAGvGAxtn1GFjEycQndYyqFSU9l4CWUwQrHzEzcVtawnIO5+GIHhneALhK3 IaMw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=foyG8pJ6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h96si16793292plb.230.2018.12.19.08.30.38; Wed, 19 Dec 2018 08:30:53 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=foyG8pJ6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729481AbeLSP7Y (ORCPT + 99 others); Wed, 19 Dec 2018 10:59:24 -0500 Received: from mail-it1-f193.google.com ([209.85.166.193]:54693 "EHLO mail-it1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727829AbeLSP7X (ORCPT ); Wed, 19 Dec 2018 10:59:23 -0500 Received: by mail-it1-f193.google.com with SMTP id i145so10383130ita.4; Wed, 19 Dec 2018 07:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L9Oe0ayTRjWuO0bO25VljJGJZxyDQt7qiLMrAfR62L4=; b=foyG8pJ6eYATlT3t/v3/QqPCjazxd7lRYM7EST/C+ScjOFHPmDTcrKjfJP34XdxJ6I E5WVVAH/uQkJfb2Ep7MPoNiacIeEP3M+H4vUTuJ0TO/sYAbl4sYHcHQbgJER6MeIGe0B GEqpaGIgebbIuVTHxWf0nBfhJcjyZcbnk4yAYyEeW9XGZ6Yyb+1SQgvU2gY22rSCBsq2 EuntTFjDJdpmjoZFx0twq8pIlmTN//Y/oaiFotdrESQbZCC5Xl+td7/DPBCpu2+07lZs wRcRLoQyeJMF448/PZuMFaAaJWy7Xd40SnU5rhhtneTGfwojfMKbfKrVwUhaKxzal5r4 +M0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L9Oe0ayTRjWuO0bO25VljJGJZxyDQt7qiLMrAfR62L4=; b=ImrkS5kPDVUJpzczdDtdCbUv+Jy+WiBcAxfpC/QOtOEzbTOB9ixV+cKFG1DEeRN+R1 8xTuFI7Y3qIQF7PEurk/3661Mxakm0f6Jtx2ptCDJO62XD4qyTl1F6jvit3i+FdA2CDr 5mt9TpXi1p3X83DGngqBgMqM57xcn/spg8ekgVGQf4buyYl0u+tPU6wZ9ds+aztCCjYK 0vX3Hfq3it2BOL/G++1VAiudQVJOoV0hwG1v0Bn+XBEwCVHQL3VsKPtMC736Km/46BQF ZbsKv4BTITQeY8O1rBQU5d8k5z4arETbO06tJV1GviADV06v4BdiSrHFUcv+NUbR5IOR xvnQ== X-Gm-Message-State: AA+aEWavp/wG7+U6dIkNqvFQfwFKf+94Ueb0Qq8gjomSQS0p/AJNT/a1 ERcfvhkIgZYobi0CTOxKwp09l/MrwNwDrXVBOyfMoA== X-Received: by 2002:a24:2d0b:: with SMTP id x11mr7439167itx.85.1545235162579; Wed, 19 Dec 2018 07:59:22 -0800 (PST) MIME-Version: 1.0 References: <1542101513-22010-1-git-send-email-firoz.khan@linaro.org> In-Reply-To: From: Matt Turner Date: Wed, 19 Dec 2018 10:59:10 -0500 Message-ID: Subject: Re: [PATCH v3 0/5] alpha: system call table generation support To: Firoz Khan Cc: linux-alpha , Richard Henderson , Ivan Kokshaysky , Thomas Gleixner , Greg Kroah-Hartman , Philippe Ombredanne , Kate Stewart , y2038 Mailman List , Linux Kernel Mailing List , Linux-Arch , Arnd Bergmann , Deepa Dinamani , Marcin Juszkiewicz Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 14, 2018 at 10:18 AM Firoz Khan wrote: > > Hi Folks, > > On Tue, 13 Nov 2018 at 15:02, Firoz Khan wrote: > > > > The purpose of this patch series is, we can easily > > add/modify/delete system call table support by cha- > > nging entry in syscall.tbl file instead of manually > > changing many files. The other goal is to unify the > > system call table generation support implementation > > across all the architectures. > > > > The system call tables are in different format in > > all architecture. It will be difficult to manually > > add, modify or delete the system calls in the resp- > > ective files manually. To make it easy by keeping a > > script and which'll generate uapi header file and > > syscall table file. > > > > syscall.tbl contains the list of available system > > calls along with system call number and correspond- > > ing entry point. Add a new system call in this arch- > > itecture will be possible by adding new entry in the > > syscall.tbl file. > > > > Adding a new table entry consisting of: > > - System call number. > > - ABI. > > - System call name. > > - Entry point name. > > > > ARM, s390 and x86 architecuture does exist the sim- > > ilar support. I leverage their implementation to > > come up with a generic solution. > > > > I have done the same support for work for ia64, m68k, > > microblaze, mips, parisc, powerpc, sh, sparc and xtensa. > > Below mentioned git repository contains more details > > about the workflow. > > > > https://github.com/frzkhn/system_call_table_generator/ > > > > Finally, this is the ground work to solve the Y2038 > > issue. We need to add two dozen of system calls to > > solve Y2038 issue. So this patch series will help to > > add new system calls easily by adding new entry in > > the syscall.tbl. > > > > changes since v2: > > - changed from generic-y to generated-y in Kbuild. > > - made changes in syscall.tbl for removing entry - > > alpha_ni_syscall. > > > > changes since v1: > > - optimized/updated the syscall table generation > > scripts. > > - fixed all mixed indentation issues in syscall.tbl. > > - added "comments" in syscall.tbl. > > - enclosed __NR_sycalls macro with __KERNEL__. > > - added missing new line. > > > > Firoz Khan (5): > > alpha: move __IGNORE* entries to non uapi header > > alpha: remove CONFIG_OSF4_COMPAT flag from syscall table > > alpha: add __NR_syscalls along with NR_SYSCALLS > > alpha: add system call table generation support > > alpha: generate uapi header and syscall table header files > > Could someone review this patch series and queue it for 4.21 > through alpha tree would be great. Thank you! I'll take a look.