Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269435AbUIILtR (ORCPT ); Thu, 9 Sep 2004 07:49:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269437AbUIILtR (ORCPT ); Thu, 9 Sep 2004 07:49:17 -0400 Received: from ozlabs.org ([203.10.76.45]:29113 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S269435AbUIILtQ (ORCPT ); Thu, 9 Sep 2004 07:49:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16704.15604.289019.476483@cargo.ozlabs.ibm.com> Date: Thu, 9 Sep 2004 21:22:28 +1000 From: Paul Mackerras To: Jakub Jelinek Cc: Benjamin Herrenschmidt , Linux Kernel list , linuxppc64-dev , Ulrich Drepper Subject: Re: vDSO for ppc64 : Preliminary release #3 In-Reply-To: <20040909091208.GY31909@devserv.devel.redhat.com> References: <1094719382.2543.62.camel@gaston> <20040909091208.GY31909@devserv.devel.redhat.com> X-Mailer: VM 7.18 under Emacs 21.3.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 18 Jakub Jelinek writes: > That is on purpose, even if vDSO location is randomized (e.g. on IA-32), > no relocations should happen, so that the vDSO can be shared (unless > written into by the debugger, that is). ld.so knows how to deal with > .dynamic section relocation of vDSOs. On 64-bit architectures which use procedure descriptors, the descriptors will have to be relocated (unless you or Alan can come up with some toolchain or ld.so magic or something). But the descriptors are in the data section rather than the text, of course. Paul. - 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/