Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2489431imu; Mon, 17 Dec 2018 02:54:10 -0800 (PST) X-Google-Smtp-Source: AFSGD/VnCoQ1JS8QKZopoEjt/QMje07G0YHYXrTEY0IolWjdIPCckISImBsZl/x5ElDAnF79DsYH X-Received: by 2002:a17:902:925:: with SMTP id 34mr11813965plm.14.1545044050051; Mon, 17 Dec 2018 02:54:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545044050; cv=none; d=google.com; s=arc-20160816; b=y/o9/YE5OTinWrrvCVfTLscbsSmpY4sM4LWyFqMfILB5doHHXxzZiwENsALN4wc1TA uwcDoDu8DZdGbnDzuJsucJkmYvk70NisKlLcVI6BEabXk9/w5YaGL3RNFzg+Sr7t5YAW tYzBfeNszCV6ApQJZi5gkh+0cy8SVrUA9sPuSzNT8RgVbBUCN8dmhf3yCPq0B79O2LYV cNEURCbXZgQ5ET3OKQv7nAoVaJjRYEWHCyf3SQOl35gMEf6fFZuxKiPoHCwykKYQ4HpJ UrKLFEgLpCAJwnLnvKQz24SJw4HMIFPVSI4ETpsI+2Le2XtGIGY7y4ROsmOj30I2gYZV 1Etw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=BtUgndAnnSH4JjWbLPwhNbGBDoT1nitXH3KyqmcxFBE=; b=ZWS7vbJUfwEwgjeCtM+xI1oRjVWpXUMSQoeqrMxXAxyggbb4vrvwkAUuhY6xWP7a3B zFqThHGZdiJexhZodyyBV501RRfVyY7SKSGIDksq7Gr/Pn6FjMra7x5adK7Oxpp3YptR YU1U7xU8PvDrT71Chd7YDp4ZY55C+Wwn3vxaR5jFWUeWIeJ7ESnCtvahOTbBz00t7xHK zzf90YxZuo7+TyReqr7GyG2IXYPtSKLPT/zZ2qsY0Lj8azEh7TLf2ajjHa35Ln7tpn31 /FEERm9p/9Swa6xlof/ePEYZcZiHk/GMbSfhWgx7PMd0vd8F5i9AkOPY1zmwMo4AexoM jj5w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cb1si10912491plb.37.2018.12.17.02.53.55; Mon, 17 Dec 2018 02:54:10 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731831AbeLQKbI (ORCPT + 99 others); Mon, 17 Dec 2018 05:31:08 -0500 Received: from ozlabs.org ([203.11.71.1]:51939 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726924AbeLQKbI (ORCPT ); Mon, 17 Dec 2018 05:31:08 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 43JHVv44stz9sBh; Mon, 17 Dec 2018 21:31:03 +1100 (AEDT) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au From: Michael Ellerman To: Satheesh Rajendran , Firoz Khan Cc: linuxppc-dev@lists.ozlabs.org, Benjamin Herrenschmidt , Paul Mackerras , Arnd Bergmann , Geert Uytterhoeven , Ram Pai , Mathieu Desnoyers , Boqun Feng , Breno Leitao , Greg Kroah-Hartman , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , linux-arch@vger.kernel.org, y2038@lists.linaro.org, linux-kernel@vger.kernel.org, marcin.juszkiewicz@linaro.org, deepa.kernel@gmail.com Subject: Re: [PATCH v5 0/5] powerpc: system call table generation support In-Reply-To: <20181217080846.GA28424@sathnaga86.in.ibm.com> References: <1544691770-8938-1-git-send-email-firoz.khan@linaro.org> <20181217080846.GA28424@sathnaga86.in.ibm.com> Date: Mon, 17 Dec 2018 21:30:58 +1100 Message-ID: <877eg8v40t.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Satheesh Rajendran writes: > Hi Firoz, > > On Thu, Dec 13, 2018 at 02:32:45PM +0530, 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. >> - Compat entry name, if required. >> - spu entry name, if required. >> >> 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 alpha, >> ia64, m68k, microblaze, mips, parisc, 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 v4: >> - DOTSYM macro removed for ppc32, which was causing >> the compilation error. >> >> Changes since v3: >> - split compat syscall table out from native table. >> - modified the script to add new line in the generated >> file. >> >> Changes since v2: >> - modified/optimized the syscall.tbl to avoid duplicate >> for the spu entries. >> - updated the syscalltbl.sh to meet the above point. >> >> Changes since v1: >> - optimized/updated the syscall table generation >> scripts. >> - fixed all mixed indentation issues in syscall.tbl. >> - added "comments" in syscall_*.tbl. >> - changed from generic-y to generated-y in Kbuild. >> >> Firoz Khan (5): >> powerpc: add __NR_syscalls along with NR_syscalls >> powerpc: move macro definition from asm/systbl.h >> powerpc: add system call table generation support >> powerpc: split compat syscall table out from native table >> powerpc: generate uapi header and system call table files > > Tried to apply on linus "master" and linuxppc-dev(https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git) "merge" branch, > both failed to apply series. > > # git am mbox > Applying: powerpc: add __NR_syscalls along with NR_syscalls > Applying: powerpc: move macro definition from asm/systbl.h > Applying: powerpc: add system call table generation support > Applying: powerpc: split compat syscall table out from native table > Applying: powerpc: generate uapi header and system call table files > error: patch failed: arch/powerpc/include/uapi/asm/Kbuild:1 > error: arch/powerpc/include/uapi/asm/Kbuild: patch does not apply > Patch failed at 0005 powerpc: generate uapi header and system call table files > Use 'git am --show-current-patch' to see the failed patch > When you have resolved this problem, run "git am --continue". > If you prefer to skip this patch, run "git am --skip" instead. > To restore the original branch and stop patching, run "git am --abort". > > Then, tried with linuxppc-dev(https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git) "next" branch, > patch got applied, compiled with ppc64le_defconfig and booted on IBM Power8 box. > > # uname -r > 4.20.0-rc2-gdd2690d2c > > Looks like patch series needs a rebase against the latest kernel versions. No it's fine if it applies on next. I can also fix up minor merge conflicts if there are any. cheers