public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linuxppc64-dev <linuxppc64-dev@lists.linuxppc.org>,
	Ulrich Drepper <drepper@redhat.com>
Subject: Re: vDSO for ppc64 : Preliminary release #3
Date: Thu, 09 Sep 2004 21:59:49 +1000	[thread overview]
Message-ID: <1094731188.2543.76.camel@gaston> (raw)
In-Reply-To: <16704.15604.289019.476483@cargo.ozlabs.ibm.com>

On Thu, 2004-09-09 at 21:22, Paul Mackerras wrote:
> 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.

In the case of the ppc vDSO, there is no .data section, the descriptors
are in the .opd section along with the .text, but that isn't a problem.
That means that 1 page of vDSO text will be COW'ed for the few apps that
request a different address (again, unless we want randomizing). The
vDSO also has a special data page that _has_ to be shared, but it's
separate and doesn't overlap the actual .so pages so it shouldn't be
affected by a possible relocation.

Of course, unless somebody comes up with a clever trick to avoid those
altogether...

Ben.



  reply	other threads:[~2004-09-09 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  8:43 vDSO for ppc64 : Preliminary release #3 Benjamin Herrenschmidt
2004-09-09  9:01 ` Benjamin Herrenschmidt
2004-09-09  9:12 ` Jakub Jelinek
2004-09-09 11:22   ` Paul Mackerras
2004-09-09 11:59     ` Benjamin Herrenschmidt [this message]
2004-09-09 12:15     ` Jakub Jelinek
2004-09-09 12:38       ` Benjamin Herrenschmidt
2004-09-09 11:55   ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1094731188.2543.76.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=drepper@redhat.com \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox