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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B7DAC10F25 for ; Mon, 9 Mar 2020 19:23:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3D9B122525 for ; Mon, 9 Mar 2020 19:23:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726486AbgCITXz convert rfc822-to-8bit (ORCPT ); Mon, 9 Mar 2020 15:23:55 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:60073 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726384AbgCITXy (ORCPT ); Mon, 9 Mar 2020 15:23:54 -0400 Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jBNzw-0005xU-TG; Mon, 09 Mar 2020 20:23:33 +0100 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id 2F3E610408A; Mon, 9 Mar 2020 20:23:32 +0100 (CET) From: Thomas Gleixner To: Mark Rutland , Vincenzo Frascino Cc: Andy Lutomirski , linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, clang-built-linux@googlegroups.com, x86@kernel.org, Catalin Marinas , Will Deacon , Arnd Bergmann , Russell King , Paul Burton , Andy Lutomirski , Ingo Molnar , Borislav Petkov , Stephen Boyd , Mark Salyzyn , Kees Cook , Peter Collingbourne , Dmitry Safonov <0x7f454c46@gmail.com>, Andrei Vagin , Nick Desaulniers Subject: Re: [PATCH v2 00/20] Introduce common headers In-Reply-To: <20200309122429.GB26309@lakrids.cambridge.arm.com> References: <20200306133242.26279-1-vincenzo.frascino@arm.com> <3278D604-28F1-47A1-BAB8-D8EB439995E8@amacapital.net> <20200309122429.GB26309@lakrids.cambridge.arm.com> Date: Mon, 09 Mar 2020 20:23:32 +0100 Message-ID: <877dzt72ob.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mark Rutland writes: > On Mon, Mar 09, 2020 at 11:07:08AM +0000, Vincenzo Frascino wrote: >> On 3/6/20 4:04 PM, Andy Lutomirski wrote: >> >> To solve the problem, I decided to use the approach below: >> >> * Extract from include/linux/ the vDSO required kernel interface >> >> and place it in include/common/ >> > >> > I really like the approach, but I’m wondering if “common” is the >> > right name. This directory is headers that aren’t stable ABI like >> > uapi but are shared between the kernel and the vDSO. Regular user >> > code should *not* include these, right? >> > >> > Would “vdso” or perhaps “private-abi” be clearer? >> >> Thanks! These headers are definitely not "uapi" like and they are meant to >> evolve in future like any other kernel header. We have just to make sure that >> the evolution does not break what we are trying to achieve with this series. > > Given we already include uapi/* headers in kernel code, I think placing > these in a vdso/* namespace would be fine. I think that more clearly > expresses the constraints on the headers than private-abi/* would. Yes, that makes most sense. Thanks, tglx