Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752933AbaFPCgK (ORCPT ); Sun, 15 Jun 2014 22:36:10 -0400 Received: from one.firstfloor.org ([193.170.194.197]:36548 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752774AbaFPCgI (ORCPT ); Sun, 15 Jun 2014 22:36:08 -0400 Date: Mon, 16 Jun 2014 04:36:04 +0200 From: Andi Kleen To: Andy Lutomirski Cc: "H. Peter Anvin" , Andi Kleen , Rich Felker , Mikael Pettersson , Russ Cox , Linux API , Ian Taylor , "linux-kernel@vger.kernel.org" , X86 ML Subject: Re: [RFC 0/2] __vdso_findsym Message-ID: <20140616023604.GI5714@two.firstfloor.org> References: <21405.44257.742122.786960@gargle.gargle.HOWL> <20140615143500.GP179@brightrain.aerifal.cx> <539DD26B.3060709@zytor.com> <539DDE9C.3010903@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At least versioning is always useful to have, just to have another tool for compatibility if changes are needed. Not sure about weak, but it can't hurt. It seems to be standard practice in glibc. I haven't looked into this in detail, but my initial assumption would be that it wouldn't be useful to add new vdso interfaces just for Go. After all would you really want to force ever Go user to upgrade their kernel just to get fast fime? So it has to work with whatever is already there anyways. I agree that current interface is not great (I didn't design it BTW, just adapted it from i386), but it should be implementable. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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/