Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932125AbaFPO7r (ORCPT ); Mon, 16 Jun 2014 10:59:47 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:57811 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932086AbaFPO7o (ORCPT ); Mon, 16 Jun 2014 10:59:44 -0400 Date: Mon, 16 Jun 2014 10:58:37 -0400 From: Rich Felker To: Andi Kleen Cc: Ian Lance Taylor , Andy Lutomirski , "H. Peter Anvin" , Mikael Pettersson , Russ Cox , Linux API , "linux-kernel@vger.kernel.org" , X86 ML Subject: Re: [RFC 0/2] __vdso_findsym Message-ID: <20140616145837.GA179@brightrain.aerifal.cx> References: <21405.44257.742122.786960@gargle.gargle.HOWL> <20140615143500.GP179@brightrain.aerifal.cx> <539DD26B.3060709@zytor.com> <539DDE9C.3010903@zytor.com> <20140616023604.GI5714@two.firstfloor.org> <20140616143801.GJ5714@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140616143801.GJ5714@two.firstfloor.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 16, 2014 at 04:38:01PM +0200, Andi Kleen wrote: > > I think this issue started when some of the Go developers questioned > > why the kernel needed to provide a very complex interface--parsing an > > ELF shared shared library--for very simple functionality--looking up > > the address of a magic function. This approach has required special > > support not just in Go, but also in the dynamic linker and gdb, and > > does not work well for statically linked binaries. The support in gdb > > is perhaps a good idea, but elsewhere it does not make sense. > > > > So why not provide a simple interface? > > What good would it do now that everyone already supports it? > > The proposal is 10+ years too late. I addressed that in one of my first emails to this thread. I don't think adding it now is immediately useful, but it will be very nice to have in a few years when optimizing for kernels from 2014 and earlier is no longer a priority. I would expect new users of vdso at that time not to bother with the ELF parsing ugliness and simply to use the lookup interface. It's not like they'd be losing any functionality on old kernels, just some performance due to falling back to the syscall. Rich -- 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/