Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750936AbaFNVaG (ORCPT ); Sat, 14 Jun 2014 17:30:06 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:57736 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750743AbaFNVaF (ORCPT ); Sat, 14 Jun 2014 17:30:05 -0400 Date: Sat, 14 Jun 2014 17:30:00 -0400 From: Rich Felker To: Andy Lutomirski Cc: Russ Cox , linux-api@vger.kernel.org, Ian Taylor , linux-kernel@vger.kernel.org, X86 ML Subject: Re: [RFC 0/2] __vdso_findsym Message-ID: <20140614213000.GO179@brightrain.aerifal.cx> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sat, Jun 14, 2014 at 11:16:42AM -0700, Andy Lutomirski wrote: > The idea is to add AT_VDSO_FINDSYM pointing at __vdso_findsym. This > implements __vdso_findsym. > > This would make it easier for runtimes that don't otherwise implement > ELF loaders to use the vdso. > > Thoughts? > > If people like the basic concept, I'll finish it, write up > documentation and a selftest. If people don't like it, I'll drop it. I like the idea. I don't think it's immediately useful, since libraries wanting to use vdso will likely want to support older kernels that don't yet have this, and thus need to include their own vdso parsing code. However, if we could get this in now, it would be very useful a few years down the line where optimizing for old kernels is not an important goal. I'd certainly like to be able to drop the ELF parsing code from musl to reduce static binary size. And I could see other projects possibly using it just to avoid the issue of ever adding ELF parsing code in the first place. 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/