From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2EDF1C433EF for ; Tue, 1 Mar 2022 16:23:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234911AbiCAQYV (ORCPT ); Tue, 1 Mar 2022 11:24:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39758 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234141AbiCAQYU (ORCPT ); Tue, 1 Mar 2022 11:24:20 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15C9C2A261; Tue, 1 Mar 2022 08:23:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=nusfBlIdbXpfMm4wiT3qTZ3hNmfr5bKSb7QSujzH1UI=; b=pYThoU2wW7VOEJiQPfBHlCMahv zqCnqvfzxIvXyQF684ZXl6dMSupAu+LBYqBkmtKoECWsWat3LCCNhroNaovFJI+jAh/R46GwYCFWE 6d9LsHuvKeoBKT/1NZn++wcdiXnUA7iTEq9BRV4a06D5/ZLyy0NczhhN5EIkVw38+CyOoVoRbLGPd 1RHj8j05KfzqDIWNx2IURQr3H7kjt9QouZEHX/fEPc0dlFoE2kebsrSqpAHLPxxWn8zTtgptkk4Hs Mb3X23j6I2kH1xwGxTp6mPvuNCMKy5E6LxKWftW7n8rUk+AHN23zUcD7XVONvOc5vnF+SaRxLhev5 eMVzBqkg==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nP5Hh-00HYWB-Bd; Tue, 01 Mar 2022 16:23:33 +0000 Date: Tue, 1 Mar 2022 08:23:33 -0800 From: Luis Chamberlain To: Arnd Bergmann Cc: Matthew Wilcox , lsf-pc@lists.linux-foundation.org, Linux FS-devel Mailing List , linux-block , Steven Whitehouse , Steve French , Samuel Cabrero , David Teigland , Namjae Jeon , Josef Bacik Subject: Re: [LSF/MM/BPF TOPIC] are we going to use ioctls forever? Message-ID: References: <20220201013329.ofxhm4qingvddqhu@garbanzo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Luis Chamberlain Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, Mar 01, 2022 at 08:47:47AM +0100, Arnd Bergmann wrote: > On Mon, Feb 28, 2022 at 10:46 PM Luis Chamberlain wrote: > > On Tue, Feb 01, 2022 at 02:14:42AM +0000, Matthew Wilcox wrote: > > > On Mon, Jan 31, 2022 at 05:33:29PM -0800, Luis Chamberlain wrote: > > > You have to get it into each architecture. Having a single place to > > > add a new syscall would help reduce the number of places we use > > > multiplexor syscalls like ioctl(). > > > > Jeesh, is such a thing really possible? I wonder if Arnd has tried or > > what he'd think... > > Definitely possible, Firoz Khan was working on this at Linaro, but he > never finished it before he left. I still have his patches if anyone wants > to pick it up, though it might be easier to start over at this point. > > The main work that is required here is to convert > include/uapi/asm-generic/unistd.h into the syscall.tbl format, > with a number of architecture specific conditionals to deal with all > the combinations of syscalls that may or may not be used on a given > target. > > After that, I would modify the scripts/syscall*.sh scripts to allow > multiple input files, splitting the architecture specific numbers > (under 400) from the newer numbers (over 400) that can be > shared between all architectures in a single location. It is not a requirement for us, but this is good to know. Thanks! Luis