From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH v2 00/20] Introduce common headers Date: Mon, 09 Mar 2020 20:23:32 +0100 Message-ID: <877dzt72ob.fsf@nanos.tec.linutronix.de> References: <20200306133242.26279-1-vincenzo.frascino@arm.com> <3278D604-28F1-47A1-BAB8-D8EB439995E8@amacapital.net> <20200309122429.GB26309@lakrids.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <20200309122429.GB26309@lakrids.cambridge.arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane-mx.org@lists.infradead.org To: Mark Rutland , Vincenzo Frascino Cc: Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, Andy Lutomirski , linux-arch@vger.kernel.org, x86@kernel.org, Russell King , clang-built-linux@googlegroups.com, Ingo Molnar , Kees Cook , Arnd Bergmann , Dmitry Safonov <0x7f454c46@gmail.com>, Borislav Petkov , Andy Lutomirski , Peter Collingbourne , linux-arm-kernel@lists.infradead.org, Andrei Vagin , Stephen Boyd , Nick Desaulniers , linux-mips@vger.kernel.org, Mark Salyzyn , Paul Burton List-Id: linux-arch.vger.kernel.org TWFyayBSdXRsYW5kIDxtYXJrLnJ1dGxhbmRAYXJtLmNvbT4gd3JpdGVzOgo+IE9uIE1vbiwgTWFy IDA5LCAyMDIwIGF0IDExOjA3OjA4QU0gKzAwMDAsIFZpbmNlbnpvIEZyYXNjaW5vIHdyb3RlOgo+ PiBPbiAzLzYvMjAgNDowNCBQTSwgQW5keSBMdXRvbWlyc2tpIHdyb3RlOgo+PiA+PiBUbyBzb2x2 ZSB0aGUgcHJvYmxlbSwgSSBkZWNpZGVkIHRvIHVzZSB0aGUgYXBwcm9hY2ggYmVsb3c6Cj4+ID4+ ICAqIEV4dHJhY3QgZnJvbSBpbmNsdWRlL2xpbnV4LyB0aGUgdkRTTyByZXF1aXJlZCBrZXJuZWwg aW50ZXJmYWNlCj4+ID4+ICAgIGFuZCBwbGFjZSBpdCBpbiBpbmNsdWRlL2NvbW1vbi8KPj4gPiAK Pj4gPiBJIHJlYWxseSBsaWtlIHRoZSBhcHByb2FjaCwgYnV0IEnigJltIHdvbmRlcmluZyBpZiDi gJxjb21tb27igJ0gaXMgdGhlCj4+ID4gcmlnaHQgbmFtZS4gVGhpcyBkaXJlY3RvcnkgaXMgaGVh ZGVycyB0aGF0IGFyZW7igJl0IHN0YWJsZSBBQkkgbGlrZQo+PiA+IHVhcGkgYnV0IGFyZSBzaGFy ZWQgYmV0d2VlbiB0aGUga2VybmVsIGFuZCB0aGUgdkRTTy4gUmVndWxhciB1c2VyCj4+ID4gY29k ZSBzaG91bGQgKm5vdCogaW5jbHVkZSB0aGVzZSwgcmlnaHQ/Cj4+ID4gCj4+ID4gV291bGQg4oCc dmRzb+KAnSBvciBwZXJoYXBzIOKAnHByaXZhdGUtYWJp4oCdIGJlIGNsZWFyZXI/Cj4+IAo+PiBU aGFua3MhIFRoZXNlIGhlYWRlcnMgYXJlIGRlZmluaXRlbHkgbm90ICJ1YXBpIiBsaWtlIGFuZCB0 aGV5IGFyZSBtZWFudCB0bwo+PiBldm9sdmUgaW4gZnV0dXJlIGxpa2UgYW55IG90aGVyIGtlcm5l bCBoZWFkZXIuIFdlIGhhdmUganVzdCB0byBtYWtlIHN1cmUgdGhhdAo+PiB0aGUgZXZvbHV0aW9u IGRvZXMgbm90IGJyZWFrIHdoYXQgd2UgYXJlIHRyeWluZyB0byBhY2hpZXZlIHdpdGggdGhpcyBz ZXJpZXMuCj4KPiBHaXZlbiB3ZSBhbHJlYWR5IGluY2x1ZGUgdWFwaS8qIGhlYWRlcnMgaW4ga2Vy bmVsIGNvZGUsIEkgdGhpbmsgcGxhY2luZwo+IHRoZXNlIGluIGEgdmRzby8qIG5hbWVzcGFjZSB3 b3VsZCBiZSBmaW5lLiBJIHRoaW5rIHRoYXQgbW9yZSBjbGVhcmx5Cj4gZXhwcmVzc2VzIHRoZSBj b25zdHJhaW50cyBvbiB0aGUgaGVhZGVycyB0aGFuIHByaXZhdGUtYWJpLyogd291bGQuCgpZZXMs IHRoYXQgbWFrZXMgbW9zdCBzZW5zZS4KClRoYW5rcywKCiAgICAgICAgdGdseAoKX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbGludXgtYXJtLWtlcm5lbCBt YWlsaW5nIGxpc3QKbGludXgtYXJtLWtlcm5lbEBsaXN0cy5pbmZyYWRlYWQub3JnCmh0dHA6Ly9s aXN0cy5pbmZyYWRlYWQub3JnL21haWxtYW4vbGlzdGluZm8vbGludXgtYXJtLWtlcm5lbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 From: Thomas Gleixner 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 Sender: linux-arch-owner@vger.kernel.org List-ID: 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 Message-ID: <20200309192332.sRXkVndunVRxU9PiGKXWReTlO-HiFunGFEUo3qYsZfA@z> 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