Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756996AbbKRUvX (ORCPT ); Wed, 18 Nov 2015 15:51:23 -0500 Received: from mout.kundenserver.de ([217.72.192.73]:62055 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756901AbbKRUvW (ORCPT ); Wed, 18 Nov 2015 15:51:22 -0500 From: Arnd Bergmann To: Yury Norov Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, pinskia@gmail.com, Prasun.Kapoor@caviumnetworks.com, schwab@suse.de, Nathan_Lynch@mentor.com, agraf@suse.de, klimov.linux@gmail.com, broonie@kernel.org, jan.dakinevich@gmail.com, ddaney.cavm@gmail.com, bamvor.zhangjian@huawei.com, philipp.tomsich@theobroma-systems.com, andrey.konovalov@linaro.org, joseph@codesourcery.com, christoph.muellner@theobroma-systems.com Subject: Re: [PATCH v6 16/19] aarch64: ilp32: use generic stat64 structure Date: Wed, 18 Nov 2015 21:45:14 +0100 Message-ID: <4142331.V6JV5koyt3@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20151118203620.GC11264@yury-N73SV> References: <1447795019-30176-1-git-send-email-ynorov@caviumnetworks.com> <4020528.IPMzSqapue@wuerfel> <20151118203620.GC11264@yury-N73SV> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:P/E7wP8gbl4DOv4WT9WEV9dy+yXJk/lDBcb3FGiePAJGp/NgKOj 3+pbQ2CC1uUXljMBKSnzggVmQlCwDN8rJb6dgqROqrK0q1J6atoXlabefERASCJ0q1ozZ4Y w1ifptGZn+F5iUdvIwrvLS4+iR0JiIWnTmMsadl3sSzm2zKM/1MIJ2aHnZs0Zfmwk/ib5Sg 3VQOtQ+zfXYrV8NHv5lIw== X-UI-Out-Filterresults: notjunk:1;V01:K0:rlsMIOkwuaM=:+GwqJbamCkZ2sLDMySE44+ 8z6ebMTyODKI3feBT/7srmjp2/q5SlSJpUhndMm6kuMi3dz8+TnCpvx7i5Op4yG80rp+Hr6C8 tMavA0P1i1aQT2+rLHAcJLUB/+ktLPaJxJxhxj2ye09X/n9ZIzXLVkL5yvD3bqeuBQSB0tADu NNBMmwJmYxfGLx8ssbwx4d7Fk57/Ii7yhJAYcdbbL5mZhFFSW661roh+SXOHN7qR+JcrGngJd 7PSkMRg52CkFHAgew2nmLGCxAsxbgMSusYtcX1jLFCDFP0IkDBQmlwwj2NEYXrZW/TPD//DcD TifLH0pBJw8fCh9OTnMNa7Rz58jTcYMzEKDpHwR4RuM84iYx8o5T48SzAZgMbUcOsCZb8e1zZ hSHYpRy0xiiVq/yFlgK18ymyV+I4OOB9e7/gPXUd+xr2XS+UWhzTpro7JRYR07B/kfZgCmoXC VmFHYWeQcbObUwUPhD4MBdwqT7h4Gt3PtrTlGKKcxXUP5M1QxNrJtMrMbgeUau/XCFj/D1l51 EK2bTR4gACO2b4UgwYp/kog7PvhAj9dmUWHfiIhT292YuL8uCtpZfXoTn8dMluz2HG9XvH4RV m9xEmfjSzGpHVjBimTS9qjjbjgMeRV/81aYLlp3TInMlbx2+JTyY4VK2+mKhZWMqGVte/4rse wAEvbBzrKCzG/5tM4RzEjcFKHLImV+UMq9WaHWkoEABNoaJBZwVbWvFlKj9XhF+Cc8c5dnD3V OzBlovaOZr0lnaaF Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1719 Lines: 42 On Wednesday 18 November 2015 23:36:20 Yury Norov wrote: > On Tue, Nov 17, 2015 at 11:09:05PM +0100, Arnd Bergmann wrote: > > On Wednesday 18 November 2015 00:16:56 Yury Norov wrote: > > > Generic 32-bit and AARCH32 stat64 structures has same names. > > > ILP32 needs generic stat64. So we can either make ILP32 mutual > > > exclusive with AARCH32, or duplicate generic cp_new_stat64 code > > > and struct stat64 to sys_ilp32.c. We choose second because it's > > > more flexible to have independend support for ABIs. > > > > > > > I commented on the previous version, but you have not replied to that, > > or changed anything. > > > > Arnd > > Hi Arnd, > > It seems I misunderstood you. > > Are you OK if we'll enable __ARCH_WANT_COMPAT_STAT64 > for ILP32, as for AARCH32_EL0, and turn glibc to use > struct stat from sysdeps/unix/sysv/linux/bits/stat.h > with this calls? It seems, this is how ARM ABI works. Yes, that's fine. The other approach I suggested was to define a stat64 structure in arch/arm64/include/uapi/asm/stat.h that has the same binary layout as 'struct stat' on arm64, and then use sys_newstat. We are doing it that way in the 64-bit time_t patch set for most architectures, and will assign a new system call number at that point as well. The only two differences between the arm32 'struct stat64' and the arm64 'struct stat' are the size of the time members and the broken __st_ino field on arm32, but that is already handled in glibc. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/