public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
	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 22:38:10 +1000	[thread overview]
Message-ID: <1094733490.2664.81.camel@gaston> (raw)
In-Reply-To: <20040909121504.GZ31909@devserv.devel.redhat.com>


> > with some toolchain or ld.so magic or something).  But the descriptors
> > are in the data section rather than the text, of course.
> 
> None of the assembly routines seem to use toc register, so if the functions
> exported from the library have special calling conventions (glibc would use
> them from inline assembly wrappers anyway), you can get away without .opd.
> vDSO is not in global search scope anyway, so applications can't call
> symbols from it anyway unless doing lots of magic.

Ok. I'm linking to the vdso directly from test apps at the moment but
that will die as soon as glibc has been adapted. Just let me know what
you prefer. I can keep the descriptors as-is and glibc would take care
of offset'ing properly when calling them, or I could try to find some
way to export different symbols like Ulrich suggested... whatever you
prefer for the glibc side.

Ben.



  reply	other threads:[~2004-09-09 12:39 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
2004-09-09 12:15     ` Jakub Jelinek
2004-09-09 12:38       ` Benjamin Herrenschmidt [this message]
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=1094733490.2664.81.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