public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@tglx.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate vsyscall/vdso gettimeofday implementations on x86_64
Date: Sun, 19 Jul 2009 09:22:10 +0200	[thread overview]
Message-ID: <20090719072210.GA3981@basil.fritz.box> (raw)
In-Reply-To: <1247954594.14494.12.camel@work-vm>

> Ok. Ulrich mailed me with the same points earlier and here's what I
> said:

Hopefully he can fix the terrible vsyscall code in glibc too.

> 1) Keep the old vsyscall gtod implementation as is, despite it
> duplicating things. Maybe avoid the code duplication via inlined
> functions.
> 
> 2) Set the old vsyscall gtod to directly call the syscall.

There were some more like

3) Call from old vsyscall into new vDSO code. This needs to store
the randomized mapping address somewhere though.
Most options required a another page for each process.

And a couple of other variants.

> Neither of these help to avoid the non-randomized syscall instruction.

They used to be patched away to nops when not needed,
unfortunately that code was removed at some point. Perhaps
that should be readded. Most systems actually don't need them
(only those that need pmtimer) 
so you don't have a static syscall entry point on them.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2009-07-19  7:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 22:02 Duplicate vsyscall/vdso gettimeofday implementations on x86_64 john stultz
2009-07-17 22:12 ` Andi Kleen
2009-07-17 22:54   ` john stultz
2009-07-18  6:07     ` Andi Kleen
2009-07-18  6:50       ` Andi Kleen
2009-07-18 22:03       ` john stultz
2009-07-19  7:22         ` Andi Kleen [this message]

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=20090719072210.GA3981@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@tglx.de \
    /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