mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ulrich Drepper" <drepper@gmail.com>
To: "Francis Moreau" <francis.moro@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64: vsyscall vs vdso
Date: Sun, 16 Sep 2007 13:46:29 -0700	[thread overview]
Message-ID: <a36005b50709161346t544d3927mfbca537c869c3c58@mail.gmail.com> (raw)
In-Reply-To: <38b2ab8a0709161324p6841c1f9h6f9422b0e6c4b5cd@mail.gmail.com>

On 9/16/07, Francis Moreau <francis.moro@gmail.com> wrote:
> I'm a bit puzzled because vdso doesn't seem to be used on my fedora 7:
> I just compiled a trivial program which just call gettimeofday() and
> ld.so resolves this call with vsyscall's gettimeofday.
>
> Now I'm wondering when vdso is used, could anybody give me a clue ?

F7 was released before the vdso for x86_64 was upstream so you should
not expect anything else.  F8 will use the available vdso.  This
doesn't just happen magically, changes to libc are needed.


> Another question: is vdso going to replace vsyscall at all ? If so how
> are statically programs going to be handled ?

Unfortunately the vsyscalls cannot ever go completely away.
Statically linked apps, the bane of progress, will need them.  There
are also people updating kernels but not the user userland code.

What we will have to do in future is to make vsyscalls configurable.
Both a compile time option and a runtime option (perhaps also under
control of SELinux) are likely needed.

  reply	other threads:[~2007-09-16 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 20:24 Francis Moreau
2007-09-16 20:46 ` Ulrich Drepper [this message]
2007-09-17  7:30   ` Francis Moreau
2007-09-17 14:35     ` Ulrich Drepper
2007-09-17 20:22       ` Francis Moreau
2007-09-18  8:31         ` Mikael Pettersson
2007-09-17 20:31   ` Francis Moreau
2007-09-18 16:58     ` Ulrich Drepper

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=a36005b50709161346t544d3927mfbca537c869c3c58@mail.gmail.com \
    --to=drepper@gmail.com \
    --cc=francis.moro@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®