From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755849Ab2LNBu2 (ORCPT ); Thu, 13 Dec 2012 20:50:28 -0500 Received: from terminus.zytor.com ([198.137.202.10]:41727 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753444Ab2LNBu1 (ORCPT ); Thu, 13 Dec 2012 20:50:27 -0500 Message-ID: <50CA85BD.7070502@zytor.com> Date: Thu, 13 Dec 2012 17:49:49 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Andy Lutomirski CC: Stefani Seibold , linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de, mingo@redhat.com, ak@linux.intel.com, aarcange@redhat.com, john.stultz@linaro.org Subject: Re: [PATCH] Add VDSO time function support for x86 32-bit kernel References: <1355343572-23074-1-git-send-email-stefani@seibold.net> <50C9148C.4040308@zytor.com> <1355378005.24283.11.camel@wall-e> <1d3061cb-76d0-4e42-9b75-a975b05384ec@email.android.com> <1355379433.24701.1.camel@wall-e> <1355383038.18653.2.camel@wall-e> <50CA6E4C.6000305@zytor.com> <50CA81A4.9040702@zytor.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/13/2012 05:42 PM, Andy Lutomirski wrote: > > The 64-bit/x32 case is currently very simple and fast because it uses > absolute addressing. Admittedly, pcrel references are free, so > changing this wouldn't cost much. For native, it'll be slower, but > maybe no one cares. I seem to care about this more than anyone else, > and I don't use 32 bit code. :) > pcrel is actually cheaper than absolute addressing in 64-bit mode. > The benefit of switching is that the vdso code could be the same in > all three cases. (Actually, it's even better than that. All of the > VVAR magic could be the same in the vdso and the kernel -- the kernel > linker script would just have to have an appropriate symbol to see the > appropriate mapping.) > > > This: > > __attribute__((visibility("hidden"))) int foo; > > int get_foo(void) > { > return foo; > } > > generates a rip-relative access on 64 bits and GOTOFF on 32 bits. > > The only reason I didn't use a real symbol in the first place is > because I couldn't figure out how to get gcc to emit an absolute > relocation in pic code. Well, then, we wouldn't need to do that... this is starting to sound like a significant win. -hpa