Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 5 May 2023 13:34:26 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Geert Uytterhoeven <geert@linux-m68k.org>
Cc:     Nhat Pham <nphamcs@gmail.com>, hannes@cmpxchg.org,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        bfoster@redhat.com, willy@infradead.org, linux-api@vger.kernel.org,
        kernel-team@meta.com
Subject: Re: [PATCH v13 2/3] cachestat: implement cachestat syscall
Message-Id: <20230505133426.d70a6599d9a729496b68a70c@linux-foundation.org>
In-Reply-To: <CAMuHMdWUtb_A-uhXrBg6kC9L2zbC_q3m8oCZoq80ZSJvk6mUAA@mail.gmail.com>
References: <20230503013608.2431726-1-nphamcs@gmail.com>
        <20230503013608.2431726-3-nphamcs@gmail.com>
        <CAMuHMdWUtb_A-uhXrBg6kC9L2zbC_q3m8oCZoq80ZSJvk6mUAA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 4 May 2023 19:26:11 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> >  arch/x86/entry/syscalls/syscall_32.tbl |   1 +
> >  arch/x86/entry/syscalls/syscall_64.tbl |   1 +
> 
> This should be wired up on each and every architecture.
> Currently we're getting
> 
>     <stdin>:1567:2: warning: #warning syscall cachestat not implemented [-Wcpp]
> 
> in linux-next for all the missing architectures.

Is that wise?  We risk adding a syscall to an architecture without the
arch maintainers and testers even knowing about it.

The compile-time nag is there to inform the arch maintainers that a new
syscall is available and that they should wire it up, run the selftest
and then ship the code if they're happy with the result.