Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5786940ybl; Tue, 14 Jan 2020 15:08:22 -0800 (PST) X-Google-Smtp-Source: APXvYqwNGMIJ2KwRiR1NISTWDEBlbYQ3kX6+Ur4sSvlthLrmGQVJfYSdqBC7lLw5+HP1I0oX3+aE X-Received: by 2002:a05:6808:52:: with SMTP id v18mr17644570oic.152.1579043302246; Tue, 14 Jan 2020 15:08:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579043302; cv=none; d=google.com; s=arc-20160816; b=E+fpS9UEzg2rMpmYy7+ppBefiy/8osTlMtWkA+W0IWnAlBFV/s1swFhrpJtWdDrR6c pE82zAqgm0770Uv8s5fgStZa0tb8iNvRFptN8JJWVVpkW32J2YH9lHSjRGy3I+Szr/ux iOcR1MNcnY4X8l4QWKcX/q+DAvIb2L6SC8khuGHxzXRA0reA4PnbXOURDJcBXJ9E4HaV x2Lm71viTDruldn6ZdF7RpJqSoayMBq3bjBZMIOuEtZCrHxuvt1RlzTMiZ7u6dvBgQu0 7J7losZ3g2XDOw/dFdJrdYwnY2xyEzDEhZ3MnCFd4EFFrGJDQd0wnZlbtIe8tTjHZ0/7 732w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=IGIvta3xATDjdvxSEzJlXFVc4DGhLxDBEPuAZnXskRg=; b=HUOuH78gO1cOIF0MNDLDWQ6tE4ZWFCzvL91SkIwPwzrR39BQc+s10xQo7tlFsdJPCL 57H1Am+fx6+IlnSmZ6Vpl7MLFjb7JUWDxUHDkCuZDz4gpGpn5KfDMnD8WoC087E+A9Uz PjmRfbKTsNPN2FdMkitpI2z0OOe3yHxvN0Zn+dGJ4aS73gPKELFpcF++yYy1KAOkstVX 3HETlRkoCb5ZpcUhmwtMXEyXEKUpvCXlPuuuu/Sb4Rb9xj6x8QfVbys8sxcwxsXgkvfm 1ZAn+rnemj6IG3g9we3pJb1F2XKodMHUqO/E/C6bCJytYDHrI8nbXrq8gqP/mDnVLsLY QWwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 77si8531180oie.10.2020.01.14.15.08.10; Tue, 14 Jan 2020 15:08:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728808AbgANXGV (ORCPT + 99 others); Tue, 14 Jan 2020 18:06:21 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:45372 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728650AbgANXGU (ORCPT ); Tue, 14 Jan 2020 18:06:20 -0500 Received: from p5b06da22.dip0.t-ipconnect.de ([91.6.218.34] 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 1irVG6-0000Gr-Ci; Wed, 15 Jan 2020 00:06:02 +0100 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id D20E7105BC2; Wed, 15 Jan 2020 00:06:01 +0100 (CET) From: Thomas Gleixner To: Christophe Leroy , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , arnd@arndb.de, vincenzo.frascino@arm.com, luto@kernel.org Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, x86@kernel.org Subject: Re: [RFC PATCH v3 08/12] lib: vdso: allow arches to provide vdso data pointer In-Reply-To: <381e547dbb3c48fd39d6cf208033bba38ad048fb.1578934751.git.christophe.leroy@c-s.fr> References: <381e547dbb3c48fd39d6cf208033bba38ad048fb.1578934751.git.christophe.leroy@c-s.fr> Date: Wed, 15 Jan 2020 00:06:01 +0100 Message-ID: <87ftghbpuu.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain 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 Christophe Leroy writes: > > static __maybe_unused int > +#ifdef VDSO_GETS_VD_PTR_FROM_ARCH > +__cvdso_clock_gettime_common(const struct vdso_data *vd, clockid_t clock, > + struct __kernel_timespec *ts) > +{ > +#else > __cvdso_clock_gettime_common(clockid_t clock, struct __kernel_timespec *ts) > { > const struct vdso_data *vd = __arch_get_vdso_data(); > +#endif > u32 msk; If we do that, then there is no point in propagating this to the inner functions. It's perfectly fine to have this distinction at the outermost level. As a related question, I noticed that you keep all that ASM voodoo in the PPC specific code which provides the actual entry points. Is that ASM code really still necessary? All current users of the generic VDSO just do something like: int __vdso_clock_gettime(clockid_t clock, struct __kernel_timespec *ts) { return __cvdso_clock_gettime(clock, ts); } in the architecture code. Is there a reason why this can't work on PPC? Thanks, tglx