From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751681AbaFMFQM (ORCPT ); Fri, 13 Jun 2014 01:16:12 -0400 Received: from terminus.zytor.com ([198.137.202.10]:43545 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750886AbaFMFQL (ORCPT ); Fri, 13 Jun 2014 01:16:11 -0400 Message-ID: <539A890A.5090206@zytor.com> Date: Thu, 12 Jun 2014 22:15:54 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andy Lutomirski , "linux-kernel@vger.kernel.org" , X86 ML , Russ Cox , Ian Taylor Subject: Re: vdso feature requests from the Go people References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/12/2014 09:36 PM, Andy Lutomirski wrote: > > If we were to implement both, maybe we'd actually want to provide > something like: > > struct vdso_entry { > unsigned long vdso_entry_struct_size; /* so we can add fields later on */ > void *func; > unsigned int max_stack; /* zero if not known */ > }; > How different is this really from the .dynsym table -- other than that you have to find the latter via the dynamic segment? The hash part is just to speed up lookup... -hpa